Comment 4 for bug 1996794
Revision history for this message
| Corey Bryant (corey.bryant) wrote Re: juju deploy machine charm with --force fails with "ERROR no releases found for channel" | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
I was asked to shed some light on the importance of --force and interim release support in this bug.
Why we are even using kinetic? For the distribution side of openstack, we provide stable support for many deb packages, and the way that we regression test them is by running suites of regression tests against juju deployed clouds. For Ubuntu SRUs, all fixes must land in the latest Ubuntu series prior to being backported to N-1 and then N-2, etc. So at this point in time, we have to land all fixes in lunar, then kinetic, then jammy, etc.
We can publish 22.10 charms to get around this, but this ends up adding cycles to work that would be free if force worked.
Thanks for taking a look at this. Very much appreciated.