Removing MAAS from a system is painful

[Raphaël Badin]

One would expect `sudo apt-get purge maas` (or something simple like that) to be enough to completely remove a MAAS installation from a system. But this doesn't work. Because of the structure of the different MAAS packages, one needs to remove a lot of packages to finally get rid of MAAS (maas-cluster-controller maas-region-controller python-django-maas, etc.)

[Andres Rodriguez (andreserl)]

Hi Raphael,

This is how APT work. If you want to remove the dependencies that were automatically installed by 'maas;, you need to:

sudo apt-get autoremove --purge

Otherwise, when you purge a package, the dependencies it installed ar market candidate for removal, but they are not removed automatically.

Marking this bug invalid.

[Andres Rodriguez (andreserl)]

roaksoax@unleashed:~$ sudo apt-get remove --purge maas
[sudo] password for roaksoax:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dbconfig-common libecap2 maas-cli maas-cluster-controller maas-common
  maas-dhcp maas-dns maas-proxy maas-region-controller
  maas-region-controller-min postgresql python-django-maas python-iscpy
  python-maas-client python-maas-provisioningserver squid-langpack squid3
  squid3-common
Use 'apt-get autoremove' to remove them.

[Raphaël Badin (rvb)]

> This is how APT work. If you want to remove the dependencies that were automatically installed by 'maas;, you need to: `sudo apt-get autoremove --purge`

Well, I understand your point but you'll admit that it's strange to do this:
`sudo apt-get purge maas`
And after that, to still have MAAS fully installed!

I mean, it's okay when a package leaves some libraries installed behind once removed (and I understand it's how API works) but in MAAS' case the *entire service* (region, cluster) is still installed and running after you uninstall the `maas` package. It's really counter-intuitive.