Cheryl just pointed out that each unit needs to have a unit agent status
doc and a workload (unit status) doc. So we can:
1 - generate a list of all the units
2 - query the status for each unit (not agent status)
3 - if it returns not found, then create the status
--
You received this bug
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.
pr: http://reviews.vapour.ws/r/3279
** Changed in: juju-core
Status: Triaged => In Progress
--
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
** Changed in: juju-core
Status: In Progress => Fix Committed
--
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 broken
To manage notifications
** Branch linked: lp:~waigani/juju-core/lxc-trusty-autostart
--
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/1271941
Title:
lxc container creation fails on trusty host service
