[2.5] MAAS doesn't notice that rack controller is no longer connected to a vlan where it was previously running DHCP, causing it to fail to configure DHCP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Critical
|
Blake Rouse |
Bug Description
MAAS was unable to configure DHCP on a rack controller, which seemed to be the rack controller that had been previously configured to a VLAN, but was no longer present in such VLAN.
DHCP HA was configured for an untagged VLAN on subnet 192.168.1.0/24, with 'charybdis' and 'ypso' as primary/secondary, respectively. However, for whatever reason, while 'ypso' as a rack controller seems to be fully connected to MAAS, there are no interfaces associated to it.
While there are no interfaces associated to it, the rack controller seems to be part of the vlan, hence as a secondary in HA.
So, while I think the real issue could be that the rack is not correctly notifying its network links, the fact that a rack disappears from a vlan and then its install a secondary rack controller is indeed an issue.
2019-02-18 14:54:47 maasserver.
Traceback (most recent call last):
File "/usr/lib/
_inlineCal
File "/usr/lib/
deferred.
File "/usr/lib/
self.
File "/usr/lib/
self.
--- <exception caught here> ---
File "/usr/lib/
current.result = callback(
File "/usr/lib/
d.
File "/usr/lib/
self.
File "/usr/lib/
raise self.value.
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
config = yield deferToDatabase
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
inContext.
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
dhcp_
File "/usr/lib/
vlan, rack_controller)
File "/usr/lib/
peer_address = get_ip_
File "/usr/lib/
return get_ip_
File "/usr/lib/
for ip_address in interface.
builtins.
Changed in maas: | |
milestone: | none → 2.5.2 |
importance: | Undecided → Critical |
status: | New → Triaged |
assignee: | nobody → Blake Rouse (blake-rouse) |
summary: |
[2.5] MAAS doesn't notice that rack controller is no longer connected to - a network where it was previously running DHCP + a network where it was previously running DHCP, causing it to traceback |
tags: | added: performance track |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in maas: | |
milestone: | 2.5.3 → 2.6.0 |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team