[2.0a1] Can't deploy a node (no interfaces on rack controller)
Bug #1554999 reported by
Dean Henrichsmeyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
I upgraded (via dist-upgrade) to 2.0.0~alpha1+
I also don't see any way of inspecting that configuration in the UI.
Related branches
lp://staging/~blake-rouse/maas/fix-1554999
- Andres Rodriguez (community): Approve
-
Diff: 93 lines (+56/-3)2 files modifiedsrc/provisioningserver/utils/network.py (+17/-1)
src/provisioningserver/utils/tests/test_network.py (+39/-2)
lp://staging/~blake-rouse/maas/fix-interface-container-discovery
- Gavin Panella (community): Approve
-
Diff: 221 lines (+37/-82)4 files modifiedsrc/provisioningserver/utils/network.py (+1/-17)
src/provisioningserver/utils/ps.py (+16/-3)
src/provisioningserver/utils/tests/test_network.py (+2/-39)
src/provisioningserver/utils/tests/test_ps.py (+18/-23)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 2.0.0 |
summary: |
- Can't deploy a node after upgrade to 2.0.0~alpha1+bzr4736-0ubuntu1 from - 1.10 + [2.0a1] Can't deploy a node after upgrade to + 2.0.0~alpha1+bzr4736-0ubuntu1 from 1.10 |
Changed in maas: | |
status: | Incomplete → Triaged |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi Dean,
can you please provide:
1. logs (var/log/ maas/*. log)
2. Is your BMC directly connected to a rack or is it routed?