[3.0.0~rc2-10023 testing] two IPs assigned to one interface
Bug #1931215 reported by
Marian Gasparovic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Björn Tillenius | ||
| 3.0 |
Fix Released
|
Critical
|
Björn Tillenius | ||
Bug Description
After MAAS is setup, juju fails with
2021-06-05-15:02:27 root DEBUG [localhost]: juju enable-ha -c foundations-maas
2021-06-05-15:02:28 root ERROR [localhost] Command failed: juju enable-ha -c foundations-maas
2021-06-05-15:02:28 root ERROR [localhost] STDOUT follows:
b''
2021-06-05-15:02:28 root ERROR [localhost] STDERR follows:
ERROR juju-ha-space is not set and a unique usable address was not found for machines: 0
run "juju controller-config juju-ha-
It seems the reason is two IPs assigned to the same interface as seen in
https:/
Related branches
~bjornt/maas:bug-1931215-3.0
- Björn Tillenius: Approve
-
Diff: 90 lines (+64/-4)2 files modifiedsrc/maasserver/models/node.py (+5/-4)
src/metadataserver/builtin_scripts/tests/test_network.py (+59/-0)
~bjornt/maas:bug-1931215-dhcp-ha-multiple-ips
- MAAS Lander: Approve
- Alberto Donato (community): Approve
-
Diff: 90 lines (+64/-4)2 files modifiedsrc/maasserver/models/node.py (+5/-4)
src/metadataserver/builtin_scripts/tests/test_network.py (+59/-0)
| Changed in maas: | |
| milestone: | none → 3.0.0-rc2 |
| importance: | Undecided → Critical |
| Changed in maas: | |
| milestone: | 3.0.0-rc2 → none |
| status: | New → In Progress |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #1 |
| tags: | added: cdo-release-blocker |
Revision history for this message
| Alberto Donato (ack) wrote | #2 |
| Changed in maas: | |
| assignee: | nobody → Björn Tillenius (bjornt) |
| Changed in maas: | |
| milestone: | none → next |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| milestone: | next → none |
To post a comment you must log in.
This is the commissioning data from one of the VMs that had multiple AUTO IPs:
https:/
So it got two IPs during commissioning. We should be able to work around this, so that we don't create any aliases during commissioning, but it would be interesting to figure out why the machine got two IPs in the first place.