Comment 6 for bug 1978125

Ok... this looks to resolve what ever was changed.... THANK YOU! I will make a note to add this to our config changes for our base images.... I take it that 22.10 didn't get this yet??? So this will be needed going forward or 22.10 solves this glitch???

This is way above my pay grade... I'd just like to get some clarity and understanding on part of this.....

My question on this is:

My BASE 22.04 VM image what we use to create a new 22.04 VM, is cloned/copied... to a VM.. then updated then. setup....

So in that cycle testing it power up, check that it still honors the pin/hold/reject file... OK, works, power down... come back to it a day later, rinse repeat, and IT WAS NOT HONORING THE PIN FILE! NO UPDATES were performed, ie: sudo apt-get update, upgrade, dist-upgrade, nothing. Just sudo apt-get -s install snapd to test.....auto-upgrades are blocked in the various config files... so what triggers this fails as expected initially, then exhibits the same behavior... that tells me something is updating stealthy that should not. Which I need to disable. We don't want anything updating till I tell it to via sudo apt-get update, upgrade|dist-upgrade etc...

Thank you again, for the solution, and I look forward to the educational reply to understand this more.. Thank you.