Recent change to juju status has broken compatibility with trusty juju-deployer
Bug #1540697 reported by
Dave Cheney
This bug report is a duplicate of:
Bug #1466128: get_cli_status assumes default format juju status is YAML.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Invalid
|
Undecided
|
Unassigned | ||
| juju-deployer |
New
|
Undecided
|
Unassigned | ||
Bug Description
The recent (2.0alpha2?) change of the default output format for juju status from yaml to tabular has broken the juju deployer that is shipped in trusty.
- Juju should revert this change
- or, juju-deployer should be updated to call juju status with the formatting it expects, and this change backported to trusty.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Invalid |
To post a comment you must log in.
We should do option 2 as Juju 2.0 will ship with tabular format by default.
Note also - obsolete status attributes are also removed in 2.0 (eg agent-state) so deployer may well require more work to be compatible. Juju 1.25 will be maintained for 2 years and will be guaranteed to work with deployer in trusty.