[2.5] Newly created VM's end up with "Error: Node must be connected to a network."
Bug #1788430 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo |
Bug Description
I added a pod and composed machines. Those machines commissioned but the network information was not updated. The UI showed:
Error: Node must be connected to a network.
After I manually commissioned the machine, the network was correctly attached.
I believe this is because on new compose it may be telling MAAS to retain network configuration?
The machine was composed with:
maas <user> pod compose <pod-id> hostname=foo cores=X memory=2048
Related branches
~mpontillo/maas:fix-skip-networking-on-compose--bug-1788430
Merged
into
maas:master
- Andres Rodriguez (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 83 lines (+43/-7)2 files modifiedsrc/maasserver/models/bmc.py (+14/-7)
src/maasserver/models/tests/test_bmc.py (+29/-0)
Changed in maas: | |
importance: | Undecided → High |
status: | New → Triaged |
importance: | High → Critical |
milestone: | none → 2.5.0alpha2 |
summary: |
- [2.5] Newly created VM's + [2.5] Newly created VM's end up with "Error: Node must be connected to a + network." |
description: | updated |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.