[2.4] PXE boot unconditionally updates interface VLAN
Bug #1750714 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
High
|
Unassigned | ||
| 2.4 |
Triaged
|
High
|
Unassigned | ||
| 2.5 |
New
|
Undecided
|
Unassigned | ||
Bug Description
When a machine boots from the network, MAAS remembers which rack controller interface observed the PXE boot, and uses that information to determine which VLAN the interface booted from.
This information is not accurate if a DHCP relay is in use, or if a non-MAAS DHCP server tells its clients to PXE boot from MAAS.
MAAS should only update the VLAN of a machine seen during a network boot if the machine has not yet been commissioned. After commissioning, the network configuration is expected to be explicitly set by the MAAS administrator.
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| milestone: | 2.4.0alpha2 → 2.4.0beta1 |
| Changed in maas: | |
| milestone: | 2.4.0beta1 → 2.4.0beta2 |
| Changed in maas: | |
| milestone: | 2.4.0beta2 → 2.4.0beta3 |
| Changed in maas: | |
| milestone: | 2.4.0beta3 → 2.4.0rc2 |
| Changed in maas: | |
| milestone: | 2.4.1 → 2.4.2 |
| Changed in maas: | |
| milestone: | 2.4.2 → 2.4.3 |
Revision history for this message
| Adam Collard (adam-collard) wrote | #3 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
What if someone picks the machine up and moves it or the cables are changed? Shouldn't MAAS handle those changes automatically, especially as we push more towards the networking be completely automated.
To me this seems like its going backwards.