When targeting the upgrade step in 1.25 I cannot see a way to distinguish between 1. a correct agent statusDoc and 2. a unit statusDoc with a agent style id - as the id is the only distinguishing feature between the two.
I imagine fwereade will hit this when writing the fix-it script. unitAgentGlobalKey was introduced in 1.22-alpha1, before then we just had unitGlobalKey. That is, Prior to 1.22-alpha1 we didn't have an agent status. If we targeted 1.22 then the upgrade step could grab all docs from statusC with format u#<name> and update them to u#<name>#charm -- 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/1516989 Title: juju status <service_name> broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
