Comment 6 for bug 1888946
Revision history for this message
| Derek DeMoss (derek-omnivector) wrote Re: image auto-sync options | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I agree with James above, this is a very common enterprise request.
My previous employers have specified various workflows to prevent minor version bug issues as he outlined above.
Some will run exactly zero updates until snapshotting a virtual machine, some will disable all automatic updates and require an early week scheduled time to run updates, and some will just not run newer versions than they test.
Not that I necessarily agree with all of those methods, but I'd like to emphasis that this is not some weird edge case but version locking is very much standard procedure in many enterprise environments, and should absolutely be a supported option.
Auto updating images have also bitten us on the Ubuntu commissioning OS side of things as well:
https:/
https:/
Were both caused by *something* being updated in Focal that broke all CentOS deployments, so while I agree that minor updates shouldn't cause issues like this, they clearly do even for Ubuntu.
Administrators should be empowered to test newer versions as they become available and select the latest working version, file bug reports when things break, and then choose to update to the next working version.