'juju deploy --force' to support not-yet-released distro?
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mojo: Continuous Delivery for Juju |
Fix Released
|
High
|
Tom Haddon | ||
Bug Description
Hi,
Sometimes, we want to test charms against not-yet-released releases (e.g. focal). This is good for testing and preparing charms to ensure that they work when it comes time to release. As per discussion with Juju devs, for these, 'juju deploy' needs to be told with --force otherwise it fails as such:
| 02:55:13 DEBUG juju.api monitor.go:35 RPC connection died
| ERROR content-cache is not available on the following series: focal not supported
| 02:55:13 DEBUG cmd supercommand.go:519 error stack:
| /build/
Maybe mojo should be updated to run 'juju deploy' with --force? Or use the results from 'ubuntu-distro-info --devel' to call 'juju deploy' with --force then?
Related branches
- Haw Loeung: Approve (+1)
- Canonical IS Reviewers: Pending requested
-
Diff: 127 lines (+39/-6)5 files modifiedMakefile (+1/-1)
debian/control (+1/-1)
mojo/phase.py (+13/-4)
mojo/tests/test_phase.py (+23/-0)
setup.py (+1/-0)
| Changed in mojo: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Tom Haddon (mthaddon) |
| Changed in mojo: | |
| status: | Confirmed → In Progress |
| Tom Haddon (mthaddon) wrote | #1 |
| Changed in mojo: | |
| status: | In Progress → Fix Released |
A fix for this has been released.