Comment 12 for bug 1089289

My understanding was that this behavior is intended, that you go for destroying the machine with all units.

My usecase is an OpenStack Deployment (small environment, not so many machines, but also not much traffic), where all the "minor" services go into one machine, but separated units. Compute gets its own machine.

Now, I wanted to extend the original installation and this required a configuration change to one of the compontents. As this setting only applies at deploy time, I had to redeploy this component. Did not work.

Your intended workflow I understand as destroy the machine and all its units - thus "the cloud" - and redeploy.

It left me frustrated. And especially the case of managing a cloud installation on bare metal with MaaS and juju seems questionable reading your statement. For most customer workloads are "cheap", I understand the vote for destroy and rebuild in this domain.