New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JUJU-2586] Fix LP19988587 Can't switch from edge channel to stable channel #15141
[JUJU-2586] Fix LP19988587 Can't switch from edge channel to stable channel #15141
Conversation
…not. Fix for LP1988587. With charm store you could update the channel to be used in the future, even if the charm itself didn't require upgrade. Allow the same behavior for charm hub charms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. QA steps confirmed. Played with it a little bit, seems to be working well 👍 Also fwiw the newly added tests are passing for me.
Unit tests and SetCharm called by the Update application facade method will not contain a charm origin. Ensure we don't panic on this in the real world. The Update facade method is only kept for compatibility with older juju 2.x clients. With juju 3.0, we can revaluate checking for an empty charm origin in the facade and updating the unit tests.
5d1b92f
to
9c50fac
Compare
A miss in commit to fix LP1988587.
Test cover scenarios in LP1988587, where refresh failed due to a lack of new available charm revision, however the switch or channel flags were used.
Add small tweeks to tests including fixing model names, correcting a charm name and enhancing comments.
2459a2f
to
823cf42
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup seems to be working well now 👍 LGTM
/merge |
#15164 Merge from 2.9 to bring forward: - #15129 from jack-w-shaw/JUJU-2615_debug_log_for_caas - #15141 from hmlanigan/198858701-refresh-switch-no-rev-change - #15154 from manadart/2.9-migration-rollback - #15157 from manadart/2.9-sync-agent-binary - #15117 from cprivitere/whitelist-10-networks Trivial conflicts.
Allow an application's channel to be updated when refreshing even if the charm revision is the same so no other change is needed. This fixes a regression in behavior between charm hub and charm store charms. Because it's a regression, only a small change was required.
QA steps
Today, all risk levels of the latest track for the ubuntu charm are the same. Makes a good test candidate.
Bug reference
https://bugs.launchpad.net/juju/+bug/1988587