Merge ~newell-jensen/maas:lp1806969 into maas:master
Proposed by
Newell Jensen
Status: | Merged |
---|---|
Approved by: | Newell Jensen |
Approved revision: | 16517d8dbfc64cc2546b1531ce63371d3547e087 |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~newell-jensen/maas:lp1806969 |
Merge into: | maas:master |
Diff against target: |
205 lines (+171/-4) 2 files modified
src/maasserver/forms/pods.py (+21/-4) src/maasserver/forms/tests/test_pods.py (+150/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Blake Rouse (community) | Approve | ||
Björn Tillenius | Needs Fixing | ||
Review via email: mp+370083@code.launchpad.net |
Commit message
LP: #1806969 -- Explicitly search for bridges, bonds, followed by the remaining interfaces when retrieving a requested machine via interface constraints.
Description of the change
The reason this bug was occurring is that the interface constraints specified were being mapped to a list of interface_ids and the max id of this list was being chosen but the the bridge interface was the one with a lower id. This branch changes how the interfaces are chosen if there is a list of interface_ids by searching for a bridge or bond and then taking the max id of this. If nothing is found or if there isn't a list of interface_ids to check, the max is taken as was done before.
To post a comment you must log in.
Why combine bridges and bonds? Should the search order be bridges first, then bonds, then other interfaces.