manual provider: adding space does not update machines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Joseph Phillips |
Bug Description
Trying to create a space on a manual provider does not refresh the subnet definition of the machine.
Reproducer:
(think of sunbeam)
- bootstrap a manual controller on the current host
- juju add-space management <one of the IP address of the host>
- juju controller-config juju-mgmt-
ERROR invalid config "juju-mgmt-
Juju will complain that the machine 0 does not have an address in this space. But the machine 0 IS the controller, and the only machine managed by the controller.
But binding the controller application to this space will actually work:
juju bind controller management
After some digging, I've seen that the machine address I'm interested in does not have a space id tagged:
{
"value": "10.206.54.40",
"addresstype": "ipv4",
"networkscope": "local-cloud",
"origin": "machine"
},
Thanks to @manadart, I've been able to look further into what's going on:
The following commands will allow the machine subnets to be tagged with a space id:
juju model-config ignore-
sudo systemctl restart jujud-machine-
juju model-config ignore-
sudo systemctl restart jujud-machine-
You can see:
{
"value" : "10.206.54.40",
"addresstype" : "ipv4",
"networkscope" : "local-cloud",
"origin" : "machine",
"spaceid" : "1"
}
but you still can't update `juju-mgmt-space`
Juju version: 3.4.2
Cloud: manual provider
description: | updated |
description: | updated |
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Joseph Phillips (manadart) |
milestone: | none → 3.4.4 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju/ juju/pull/ 17455
This cuts the process down to one bounce of the agent post space definition.