Hi all, I have an Xenial Mitaka Openstack deployed with juju 1.25.5 and maas 1.9.2 from a Trusty deployment host.
I'm having troubles with a juju subordinate charm that didn't initialise when I first deployed it, and now I'm unable to get rid of it. I have a cs:ubuntu charm deployed to the only state server (not HA due to bug LP#1575448), and a landscape-client subordinate which didn't start up. It was left in an agent-state of allocating, with a message of "Waiting for agent initialization to finish." After some discussion on #juju-dev, it was suggested that the best way to fix it would be to juju destroy-unit on the ubuntu charm, which should clean up the unwanted instance. I added another unit to the state server, and then did a juju destroy-unit on the unwanted one - unfortunately, this led me to the state where the main charm is in a terminating state, seemingly waiting for the subordinate to come up. The only evidence of the subordinate on the machine is what seems to be a partially filled out agent.conf. Does anyone have any suggestions on how to clean up the unwanted subordinate? I think once that is done the main charm will finish terminating, and I'll be in a good state. Please let me know if there's any more information needed. Thanks, Brad -- Brad Marshall Cloud Reliability Engineer BootStack Squad, Canonical -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
