Merge ~ltrager/maas:lp1911825_2.9 into maas:2.9
Proposed by
Lee Trager
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Lee Trager | ||||
Approved revision: | 835dfd7ed5346a347510b7019b757edd43b7a679 | ||||
Merge reported by: | MAAS Lander | ||||
Merged at revision: | not available | ||||
Proposed branch: | ~ltrager/maas:lp1911825_2.9 | ||||
Merge into: | maas:2.9 | ||||
Diff against target: |
99 lines (+33/-15) 2 files modified
src/maasserver/models/bmc.py (+25/-6) src/maasserver/models/tests/test_bmc.py (+8/-9) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lee Trager (community) | Approve | ||
Review via email: mp+396626@code.launchpad.net |
Commit message
LP: #1911825 - Don't set BMC.ip_address when power_address contains an FQDN
When a BMC is created or edited MAAS maps its IP address to a subnet which
is stored in the model. This allows MAAS to send power commands only to
rack controllers which are on the same subnet as the BMC. If no rack
controller is on the same subnet as the BMC the power command is sent to
all rack controllers. When an FQDN or hostname were given an exception was
raised as MAAS expected an IP address. The exception is now avoided so the
fallback code is used which allow for FQDN or hostnames in the
power_address.
Backport of 19a09e6
To post a comment you must log in.