Juju 3 is not supported
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mojo: Continuous Delivery for Juju |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
Attempting a deploy on my laptop, running the latest/stable Juju snap (3.2 at time of writing) gives:
2023-05-30 16:40:19 [ERROR] Unknown error
Traceback (most recent call last):
File "/snap/
args.func(args)
File "/snap/
return method(*args, **kwargs)
File "/snap/
manifest.
File "/snap/
phase_
File "/snap/
self.
File "/snap/
raise BundlePhaseExce
mojo.phase.
This is because the detection code here looks for both 2+ for the major version, and 3+ for the minor version - 3.2 actually supports everything we're trying to gate here, but the code doesn't know about it:
https:/
Related branches
- Tom Haddon (community): Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 35 lines (+6/-6)2 files modifiedmojo/juju/status.py (+5/-5)
mojo/phase.py (+1/-1)
- Haw Loeung: Approve (+1)
- Canonical IS Reviewers: Pending requested
-
Diff: 194 lines (+35/-15)8 files modifiedmojo/contain.py (+5/-1)
mojo/juju/debuglogs.py (+9/-2)
mojo/juju/utils.py (+8/-2)
mojo/juju/wait.py (+4/-2)
mojo/phase.py (+1/-1)
mojo/tests/test_debuglogs.py (+3/-2)
mojo/tests/test_mojo.py (+4/-4)
mojo/tests/test_utils.py (+1/-1)
| Changed in mojo: | |
| importance: | Undecided → Critical |
| Changed in mojo: | |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
Just want to add that while fixing this particular specific check looks relatively simple, there are many, many version checks throughout the code and a whole suite of juju2-specific tests.
Adding juju3 support should really be done properly, if it's going to be added.