[2.1+, UI] Hard to tell that HA is not enabled for DHCP on a VLAN
Bug #1675981 reported by
Peter Matulis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Steve Rydz |
Bug Description
A complete MAAS environment was installed via the 'maas' metapackage. On another host I installed and registered a second rack controller, to achieve HA on the rackd level. I confirmed that both rackd were recognized in the region (via web UI and CLI). Nodes could be enlisted, commissioned and deployed using MAAS-managed DHCP.
To test HA, the original rackd was turned off:
sudo service maas-rackd stop
I was expecting DHCP to become available, via the second rackd, but this wasn't the case. It never came on. This was reflected in the web UI ('dhcpd' was not green). Enlistment and Deployment (two different nodes) also failed.
2.2.0~beta3+
Changed in maas: | |
status: | Triaged → Invalid |
Changed in maas: | |
status: | Invalid → Triaged |
Changed in maas: | |
assignee: | nobody → Lilyana Videnova (lilyanavidenova) |
Changed in maas: | |
assignee: | Lilyana Videnova (lilyanavidenova) → Steve Rydz (steverydz) |
status: | Triaged → In Progress |
milestone: | next → 2.6.0rc1 |
Changed in maas: | |
milestone: | 2.6.0rc1 → 2.6.0rc2 |
Changed in maas: | |
milestone: | 2.6.0rc2 → 2.7.0beta1 |
Changed in maas: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Did you set the secondary rack controller as the "secondary_rack" on the VLAN that is providing DHCP. Setting up the HA is a manual process, once setup it allows one of those two racks on that VLAN to go down that is it.