Manual provider error on re-configuring HA
This bug report will be marked for expiration in 55 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Similar to https:/
Running on 3.4.4, I am trying to boostrap juju with manual cloud and enable ha:
juju enable-ha -n 3 --to 1,2
This is working. Then I add a new machine (3) to the cluster and I have machines 0, 1, 2, 3
Then I want to remove machine 2: juju remove-machine 2
Then I want to re-enable ha but use the machine 3: juju enable-ha -n 3 --to 3
Then I get the same error as the similar bug I linked in the beginning:
ubuntu@maas-1:~$ juju enable-ha -n 3 --to 3
ERROR juju-ha-space is not set and a unique usable address was not found for machines: 0
run "juju controller-config juju-ha-
ubuntu@maas-1:~$ juju show-machine 0
model: controller
machines:
"0":
juju-status:
current: started
since: 24 Jul 2024 13:07:38Z
version: 3.4.4
hostname: maas-1
dns-name: 10.20.0.62
ip-addresses:
- 10.20.0.62
- 10.20.0.80
instance-id: 'manual:'
machine-status:
current: running
message: Manually provisioned machine
since: 24 Jul 2024 13:07:38Z
modificatio
current: idle
since: 24 Jul 2024 13:07:30Z
base:
name: ubuntu
channel: "22.04"
network-
enp5s0:
- 10.20.0.62
- 10.20.0.80
gateway: 10.20.0.1 10.20.0.1
space: alpha
is-up: true
constraints: arch=amd64 mem=3584M
hardware: arch=amd64 cores=4 mem=7930M
controller-
ha-primary: true
Changed in juju: | |
status: | New → Incomplete |
Was the second of the addresses added post-bootstrap?