** Description changed: - Report from the field, a service with no units (previously destroyed) is - stuck in lifecycle dying. Per status snippet + [Impact] + Services will no service units get stuck in 'dying' state preventing their removal from a deployment. + + [Test Case] + juju deploy mysql + juju terminate-machine --force <machineid of mysql> + juju destroy-service mysql + + [Regression Potential] + Part of the upstream tested 1.16.6 release. Change looks limited to impacted code path only + + [Original Report] + [Report from the field, a service with no units (previously destroyed) is stuck in lifecycle dying. Per status snippet mysql: - charm: local:precise/mysql-309 - exposed:false - life: dying - relations: - cluster: - - mysql + charm: local:precise/mysql-309 + exposed:false + life: dying + relations: + cluster: + - mysql
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1233457 Title: service with no units stuck in lifecycle dying To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1233457/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
