Using pacemaker VIP addresses in dhcpd.conf
Bug #2027736 reported by
Jorge Merlino
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
This issue can occur in HA installations where there are VIP addresses assigned by pacemaker on the same VLAN where DHCP is enabled. MAAS could choose a secondary VIP address and use it in the address and/or peer address parameters on the failover DHCP configuration on dhcpd.conf. In the event of a failover, the IP will be moved somewhere else and this configuration would be incorrect.
It seems that MAAS does not check for this when building the failover configuration in the make_failover_
I was able to reproduce it in snap version 3.2.8-12050-
tags: | added: dhcp |
Changed in maas: | |
status: | Incomplete → Triaged |
milestone: | none → 3.5.0 |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.x |
To post a comment you must log in.
Can reproduce. MAAS does not currently have a way of differentiating a VIP from pacemaker and a regularly assigned IP on an interface.
Separate, if using the Ansible Playbooks, the VIP is only for the Postgres primary. If you can separate the rack controllers from those hosts (ideal for HA), this can be worked around.