Not assigning static IP addresses
Bug #1363999 reported by
Jeroen T. Vermeulen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Julian Edwards |
Bug Description
With an installed MAAS upgraded to a package built from fresh trunk today, I'm not seeing static IP addresses on my nodes. The managed cluster interface has a static range, yet the nodes, even when deployed, have addresses in the dynamic range.
This may have happened as a consequence of recent IPv6 work, which was supposed to give a MACAddress a StaticIPAddress for each managed NodeGroupInterface to which it is connected — which may include both an IPv4 and an IPv6 one.
Related branches
lp:~julian-edwards/maas/update-mac-to-cluster-when-updating-leases
- Jeroen T. Vermeulen (community): Approve
-
Diff: 67 lines (+35/-0)2 files modifiedsrc/maasserver/rpc/leases.py (+2/-0)
src/maasserver/rpc/tests/test_regionservice.py (+33/-0)
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The reason appears to be that MACAddress. cluster_ interface isn't populated. It may be a matter of waiting for the next DHCP leases uploaded to set this right.