Upgrades from 1.20.11 to 1.25.2 fail because of status
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Undecided
|
Unassigned | ||
1.25 |
Fix Released
|
Critical
|
Tim Penhey |
Bug Description
As seen in
http://
The aws-upgrade-
The results are consistent for 1.25.2. in 5 retests. In the example, after the call to upgrade, the script starts polling the progress using status. we see two dots indicating the first two calls to status occurred quickly
1.20.11: 1, 0, 2, dummy-sink/0, dummy-source/0 ..
but the 3rd call to status hung for 300 seconds. At that point a timeout is raised because there was no visibility into to the progress of the upgrade. By the time the script reports this, we often see the upgrade has succeeded or is very near completion.
So we know upgrades work. anyone who interrupted the hung status and tried again would probably see that status succeed and that the upgrade was progressing.
1.20.11: 1, 0, 2, dummy-sink/0, dummy-source/0 ..
2015-11-25 07:59:28 ERROR Timed out waiting for juju status to succeed: Command 'juju' returned non-zero exit status 1
Traceback (most recent call last):
File "/mnt/jenkinsho
yield
File "/mnt/jenkinsho
assess_
File "/mnt/jenkinsho
client.
File "/mnt/jenkinsho
versions = self.get_
File "/mnt/jenkinsho
'Timed out waiting for juju status to succeed: %s' % e)
Exception: Timed out waiting for juju status to succeed: Command 'juju' returned non-zero exit status 1
The python script is calling juju status. it parses the yaml and returns a helper to get data out of status.
Changed in juju-core: | |
status: | New → Incomplete |
tags: | added: blockr |
tags: |
added: blockrer removed: blockr |
tags: |
added: blocker removed: blockrer |
Changed in juju-core: | |
status: | Incomplete → Invalid |
Juju-CI verified that this issue is Fix Released in juju-core 1.25: reports. vapour. ws/releases/ 3374
http://