cannot remove and re-add a manually provisioned machine

[Andrea Ieri]

Expected behavior:
Removing a manually provisioned machine cleans up all deployed juju code

Current behavior (2.6.9):
Manual cleanup is needed to re-deploy a manually provisioned machine

How to reproduce:
$ juju add-machine ssh:ubuntu@<some-IP>
created machine 64
$ juju remove-machine 64
removing machine 64
$ juju add-machine ssh:ubuntu@<some-IP>
ERROR machine is already provisioned

Workaround:
$ sudo systemctl disable jujud-machine-64.service
Removed /etc/systemd/system/multi-user.target.wants/jujud-machine-64.service.
Removed /etc/systemd/system/jujud-machine-64.service.
$ sudo rm -rf /lib/systemd/system/jujud-machine-64
$ sudo rm -rf /var/lib/juju
# Now add-machine will work

[Joseph Phillips (manadart)]

The removal of cleanup logic was a deliberate step to ensure that no Juju infrastructure can self-destruct under any circumstances.

As a compromise, machine initialisation has been modified to add an executable script to /sbin for cleaning a controller or machine previously provisioned by Juju.

So there is still a manual step required, but it is simply "/sbin/remove-juju-services".

The patch is here: https://github.com/juju/juju/pull/10877

[Joseph Phillips (manadart)]

This actually went out with 2.7.1.