Great idea, John \o/ Marked as hidden now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Should I mark comment #16 as "hidden" so it doesn't give people the
wrong idea?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this b
WARNING: don't use the script in comment #16, but instead use this one:
http://pastebin.ubuntu.com/24186473/
This is a copy of the earlier script but adds in the txn-revno and txn-
queue fields that are required for when juju wants to update the status
to something new.
--
You received this bug
** Changed in: juju-core
Milestone: 2.0-alpha1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
https://bug
** Changed in: juju-core/1.25
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go
The script to address this bug is here:
http://paste.ubuntu.com/14474251/
Steps to resolve this issue:
- On the state server, install mongodb-clients (installs the mongo tool to
allow us to manually modify the database)
- Run the insert-statuses.sh script on the state server (machine 0):
./inser
Not fixing in 2.0, as users will be required to upgrade to 1.25.2 before
upgrading to 2.0
** Changed in: juju-core
Status: In Progress => Invalid
** Changed in: juju-core
Status: Invalid => Won't Fix
** Changed in: juju-core
Status: Won't Fix => Invalid
--
You received thi
** Changed in: juju-core
Milestone: 1.26-alpha3 => 2.0-alpha1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-cor
Just a note to those using the script to insert the workload status -
you'll see a bogus time in the "since" field: 31 Dec 1969
18:00:00-06:00
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Ti
I confirm the fix is effective. For large environments where hooks have failed,
here's a one-liner after running the fix to re-run all the failed hooks, which
should return the agents to normal (idle) state:
for i in `juju status --format tabular|grep failed|awk '{print $1;}'`;do echo
Fixing $i;
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Fix Committed
** Changed in: juju-core/1.25
Importance: Undecided => Critical
** Changed in: juju-core/1.25
Assignee: (unassigned) => Jesse Meek (waigani)
** C
** Changed in: juju-core
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications about this bug go to:
h
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifi
The fix for this is underway, and should be included in 1.25.2.
William kindly put together a script to directly modify mongo to add in
the missing statuses to work around this problem in the meantime. You
can contact me directly to get the script until I figure out where to
put it.
I have verif
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 notifi
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.
unitAgentGl
** Changed in: juju-core
Assignee: Cheryl Jennings (cherylj) => Jesse Meek (waigani)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications ab
fwereade is working on a script to repair an environment after this is
hit in an upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifications ab
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516989
Title:
juju status broken
To manage notifi
21 matches
Mail list logo
