Re-commissioning doesn't detect storage changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo | ||
1.9 |
Fix Released
|
Critical
|
Mike Pontillo |
Bug Description
I have a node that had recently more disks added including new SSD. I re-commissioned it but new storage devices are not showing in MAAS UI (see attachment)
When I look at commissioning output relevant hardware is showing there for example:
<lshw:node id="disk:1" claimed="true" class="disk" handle=
un maas <none> <none> (no description available)
ii maas-cli 1.9.1+bzr4543-
un maas-cluster-
ii maas-common 1.9.1+bzr4543-
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.1+bzr4543-
ii maas-proxy 1.9.1+bzr4543-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.1+bzr4543-
ii python-maas-client 1.9.1+bzr4543-
ii python-
Related branches
- Blake Rouse (community): Approve
- Andres Rodriguez (community): Needs Information
-
Diff: 48 lines (+27/-0)2 files modifiedsrc/metadataserver/models/commissioningscript.py (+9/-0)
src/metadataserver/models/tests/test_commissioningscript.py (+18/-0)
- Mike Pontillo (community): Approve
-
Diff: 69 lines (+37/-0)3 files modifieddocs/changelog.rst (+10/-0)
src/metadataserver/models/commissioningscript.py (+9/-0)
src/metadataserver/models/tests/test_commissioningscript.py (+18/-0)
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 1.9.3 |
Changed in maas: | |
milestone: | 1.9.3 → 2.0.0 |
status: | Incomplete → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I uploaded full commissioning output here: /private- fileshare. canonical. com/~jacek/ lp1575567. xml
https:/