[2.3] Re-installation fails with "Volume already exists"

[Ketan Adkar]

We have MAAS 2.3 installed however when I release a machine & select option "erase disk before release" and "use secure erase" then MAAS goes & deletes the LVM/RAID volumes from the server however the entries in MAAS DB are not cleared out. Maas still thinks that the LVM/RAID volumes still exist on the server (even though they do not) after releasing the machine & as a result of which it fails during deployment with the error "Volume already exists".
I think this is a bug as MAAS is not updating its DB even after deleting the volumes on the server.
So is there a way/hook to tell to MAAS update its DB when it releases the machines & deletes the LVM/RAID configuration on the servers?

Is anyone else also facing this issue ?

Output of : 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
+++-===============================-====================================-============-=============================================
un maas <none> <none> (no description available)
ii maas-cli 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.3.0-6434-gd354690-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.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.3.0-6434-gd354690-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

[Andres Rodriguez (andreserl)]

Hi Ketan,

The secure erase doesn't work on all disks. So it could be that your disks do not support secure erase. Can you try quick erase and report back?

That said, curtin does the storage configuration so it should be ensuring it can erase whatever is was previously installed to re-install.

[Andres Rodriguez (andreserl)]

Argh! I submitted the comment to early.

Note that MAAS only *models* how you want your disk partitioned. So if you release and re-deploy a machine, curtin, the tool that does the storage config for MAAS would have to repartioning the disk.

So this seems that curtin is not doing so. Could you please provide:

1. Installation log (Machine details page > Installation)
2. The sent to the failed deployment machine (maas <user> machine get-curtin-config <system-id>)

[Andres Rodriguez (andreserl)]

Oh, and one more thing. What's the curtin version you are using:

dpkg -l | grep curtin.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for curtin because there has been no activity for 60 days.]