I have been trying to recommission a system for which a set of disks had not previously been initialized.
After initializing them via the controller setup menu during POST and recommissioning, maas would not list them as storage even though lshw showed those disks. I tried going into the commissioning environment and could access the disks without any issue. Then I decided to delete and re-enlist the system and now they are showing up.
I never selected retain storage configuration so could this option actually be set by default?
This looks to be easy to recreate. I have attached content of node page from the UI as well as lshw before and after re-enlisting.
I re-created with an HP system for which RAID got enabled (and so 4 disks weren't being discovered) and after I deleted the RAID and disabled the controller, maas still wouldn't show the disks.
Then, following deletion and re-enlistment of that server, maas started showing the disks. I had not checked the lshw output as I didn't initially think the 2 issues were related, but now I see that this is a re-create.
ubuntu@maas2-production-new:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-==============================-============-=================================================
ii maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.1.3+bzr5573-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.1.3+bzr5573-0ubuntu1~16.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.1.3+bzr5573-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)
Please provide the output of:
"maas session block-devices read {system_id}"
And the output of the commissioning result:
00-maas- 07-block- devices