enable-ha command does not work with placement directive --to

Bug #1832393 reported by Pedro Guimarães
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
New
Undecided
Unassigned

Bug Description

Juju 2.6.3 (snap / stable channel)

Deployed a manual controller provider and added machines to controller model with:

juju add-machine -m controller ssh:ubuntu@A.B.C.D
Machine added got serial code 1

Then, ran enable-ha on this controller with:

juju enable-ha -n 1 --to 1 (added machine code)

Machine 1 was successfully added to controller model and I can see jujud-machine-1.service is running correctly.
However, there is no evidence of a controller was deployed on this node after enable-ha (e.g. no juju-db.service is present or telnet to localhost:17070 is refused).

Therefore, I see no way to run manual provider controller on ha mode.

Bug: https://bugs.launchpad.net/juju/+bug/1357760 is similar to this issue, however I am using command and placement directive described on "juju enable-ha --help" to try to get my controller to ha mode.

Tags: cpe-onsite
Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

I've just tested juju from edge channel and it is working.
The way to run it is:

juju add-machine ... --> create machines 1 and 2 on model controller
juju enable-ha --to=1,2

According to rick_h, this merge is the one responsible for the new feature: https://github.com/juju/juju/pull/10185

tags: added: cpe-onsite
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.