Commissioning fails if NIC gets different PCI address
Bug #1923867 reported by
Björn Tillenius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Lee Trager |
Bug Description
This is with MAAS 3.0.0~beta3 (9853-g.28bad2fcb)
I added some PCI devices to a machine in MAAS, and as
a result, an existing NIC got another PCI address.
This makes commissioning fail:
https:/
We sort of handle the case where PCI devices move, but we
never look at what the validation error is. So in this case
we try to remove the wrong device before creating a new one.
Related branches
~ltrager/maas:lp1923867
Merged
into
maas:master
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 239 lines (+170/-5)3 files modifiedsrc/maasserver/testing/factory.py (+2/-1)
src/metadataserver/builtin_scripts/hooks.py (+32/-4)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+136/-0)
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.0.0 → 3.0.0-beta5 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I attached the old commissioning data before the PCI devices were changed, and the new, where the processing fails.
The device that causes problem is "RTL8125 2.5GbE Controller"