Merge lp:~jameinel/juju-core/1.18-dowgrade-patch-level into lp:juju-core/1.18
Status: | Merged |
---|---|
Approved by: | Ian Booth |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2267 |
Proposed branch: | lp:~jameinel/juju-core/1.18-dowgrade-patch-level |
Merge into: | lp:juju-core/1.18 |
Diff against target: |
183 lines (+95/-30) 3 files modified
worker/upgrader/export_test.go (+4/-1) worker/upgrader/upgrader.go (+40/-28) worker/upgrader/upgrader_test.go (+51/-1) |
To merge this branch: | bzr merge lp:~jameinel/juju-core/1.18-dowgrade-patch-level |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ian Booth | Approve | ||
Review via email: mp+215282@code.launchpad.net |
Commit message
This backs off a little bit on the "refuse to downgrade" to "refuse to downgrade across MAJOR or MINOR versions".
This allows the CI infrastructure to continue to test 'upgrades' when Juju will default to bootstrapping a version that is newer than the target of the test. (they *want* to bootstrap 1.18.0 and then upgrade it to 1.18.1, but bootstrap will go immediately to 1.18.1, so they have to bootstrap, downgrade, and then upgrade again. Not an ideal situation.)
If it was just CI, then I might push harder to fix it elsewhere, but I can see users getting a bugfix patch that actually breaks something and needing a way out.
We still refuse to go across MAJOR or MINOR versions, because we almost definitely are going to be changing things like agent.conf there and when they get to the target version, it will just be broken.
Description of the change
This backs off a little bit on the "refuse to downgrade" to "refuse to downgrade across MAJOR or MINOR versions".
This allows the CI infrastructure to continue to test 'upgrades' when Juju will default to bootstrapping a version that is newer than the target of the test. (they *want* to bootstrap 1.18.0 and then upgrade it to 1.18.1, but bootstrap will go immediately to 1.18.1, so they have to bootstrap, downgrade, and then upgrade again. Not an ideal situation.)
If it was just CI, then I might push harder to fix it elsewhere, but I can see users getting a bugfix patch that actually breaks something and needing a way out.
We still refuse to go across MAJOR or MINOR versions, because we almost definitely are going to be changing things like agent.conf there and when they get to the target version, it will just be broken.