Merge ~ltrager/maas:lp1816651 into maas:master
Proposed by
Lee Trager
Status: | Merged |
---|---|
Approved by: | Lee Trager |
Approved revision: | 326d99566d56686a4e0bc103be14582e9679e620 |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~ltrager/maas:lp1816651 |
Merge into: | maas:master |
Diff against target: |
67 lines (+29/-8) 2 files modified
src/maasserver/models/bmc.py (+9/-7) src/maasserver/models/tests/test_bmc.py (+20/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mike Pontillo (community) | Approve | ||
MAAS Lander | Approve | ||
Review via email: mp+363520@code.launchpad.net |
Commit message
LP: #1816651 - Handle duplicate IP addresses when creating a BMC object.
To post a comment you must log in.
Can you see if this slightly simpler change does the trick?
https:/ /paste. ubuntu. com/p/cxqZqmzZH C/
I don't think this change will work as intended, since the BMC IP might be an AUTO IP, not strictly a STICKY. For example, if I deploy a machine and use it for a KVM pod, it might get an AUTO address (or even DHCP), rather than STICKY.