enable-ha requires '-m controller' (i.e. doesn't do the 'right thing' by default).
Bug #1607170 reported by
Christopher Lee
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Menno Finlay-Smits | ||
Bug Description
Using the command: juju enable-ha
Results in the error message: ERROR unsupported with hosted models
What I actually have to type is: juju enable-ha -m controller
enable-ha should do this by default as it's dealing with controllers.
Also, the examples in the --help output use an example which will results in an error message:
Examples:
# Ensure that the controller is still in highly available mode. If
# there is only 1 controller running, this will ensure there
# are 3 running. If you have previously requested more than 3,
# then that number will be ensured.
juju enable-ha
... snip ...
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0-rc1 |
| tags: | added: usability |
| tags: | added: ha |
| Changed in juju-core: | |
| milestone: | 2.0-rc1 → 2.0.0 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → 2.0-rc1 |
| assignee: | nobody → Alexis Bruemmer (alexis-bruemmer) |
| Changed in juju: | |
| milestone: | 2.0-rc1 → 2.0-rc2 |
| Changed in juju: | |
| milestone: | 2.0-rc2 → none |
| Changed in juju: | |
| milestone: | none → 2.0.0 |
| tags: | added: ateam |
| Changed in juju: | |
| assignee: | Alexis Bruemmer (alexis-bruemmer) → Menno Smits (menno.smits) |
| Changed in juju: | |
| milestone: | 2.0-rc3 → 2.0.0 |
| Changed in juju: | |
| status: | Triaged → In Progress |
Revision history for this message
| Menno Finlay-Smits (menno.smits) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix: https:/