Adding an IP alias to the MAAS server causes IntegrityError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
This is MAAS 1.7.1RC2.
After setting up a region and cluster on the same host, I added an alias to the interface that is being managed by MAAS, eth0:1. This caused an OOPS to be registered:
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
self.run()
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
return self.cursor.
File "/usr/lib/
File "/usr/lib/
return self.cursor.
django.
DETAIL: Key (name, address, port)=(
The IP address on the alias was for a subnet different from the main subnet on the host.
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas: | |
status: | Triaged → Invalid |
I'm having a hard time reproducing this, can you please provide more information about your setup: name, interface, IP, management for the existing cluster interfaces and the new one?