Also, when in this situation, sometimes a unit agent restart can force a failure, at which point you can force the unit to resolve and typically it will be cleaned up.
But the remove-machine --force is a definitely a better option if it's along on the machine. Use the --force, Luke. On Fri, Sep 01, 2017 at 12:52:03AM +0000, Rick Harding wrote: > Is it alone on that container on machine 1 - container 12? If so you can > > juju remove-machine --force 1/lxd/12 > > On Thu, Aug 31, 2017 at 8:08 PM Giuseppe Attardi <[email protected]> > wrote: > > > I am not able to remove an openstack-dashboard application from a model, > > because apparently there is no registered hook for stop in the charm and > > the log shows: > > > > INFO juju-log Unknown hook stop - skipping. > > > > and juju status shows: > > > > App Version Status Scale Charm > > Store Rev OS Notes > > openstack-dashboard 11.0.2 terminated 1 openstack-dashboard > > jujucharms 247 ubuntu > > > > Unit Workload Agent Machine Public > > address Ports Message > > openstack-dashboard/2* terminated executing 1/lxd/12 90.147.161.39 > > 80/tcp,443/tcp (stop) > > > > How can I get rid of it? > > > > — > > > > > > > > > > -- > > Juju mailing list > > [email protected] > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/juju > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju -- James Hebden Cloud Reliability Engineer BootStack Squad @ Canonical Ltd. -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
