MAAS doesn't detect the right PXE interface
Bug #1847046 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Björn Tillenius | ||
| 2.6 |
Fix Released
|
High
|
Björn Tillenius | ||
Bug Description
MAAS detects which NIC that was used during the PXE boot process and marks it such in the API and UI. This ssh:ing to the machine when it's in rescue mode easier, since you know which interface that is being brought up.
However, if the machine boots from PXE using the UUID path, rather than the MAC path, then MAAS doesn't detect which NIC is the PXE boot interface and just marks the first one as such.
This means that in a lot of cases, MAAS will mark the wrong interface. In our internal CI, the test_enter_
We do capture the kernel command line that was being used during commissioning, so we could parse that and look which MAC was passed to BOOTIF.
Related branches
~bjornt/maas:bug-1847046-pxe-boot-interface-2.6
- Björn Tillenius: Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 310 lines (+202/-3)5 files modifiedsrc/maasserver/rpc/boot.py (+5/-1)
src/maasserver/rpc/tests/test_boot.py (+35/-0)
src/metadataserver/builtin_scripts/hooks.py (+43/-0)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+106/-1)
src/provisioningserver/refresh/node_info_scripts.py (+13/-1)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Björn Tillenius (bjornt) |
| milestone: | none → 2.7.0alpha1 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
