Restore-backup model is not usable because upgrade in progress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
As seen in
http://
The controller was restored. The config was set on an app to prove the model was usable. The call failed because Juju thinks an upgrade is in progress. An upgrade cannot be in progress because the juju under-test is the newest version.
ERROR cmd supercommand.go:458 upgrade in progress (upgrade in progress)
2016-11-02 15:08:00 ERROR Command '('juju', '--show-log', 'config', '-m', 'functional-
Traceback (most recent call last):
File "/var/lib/
yield
File "/var/lib/
yield machines
File "/var/lib/
assess_
File "/var/lib/
check_
File "/var/lib/
client.
File "/var/lib/
self.
File "/var/lib/
model, check, timeout, extra_env)
File "/var/lib/
rval = call_func(args)
File "/usr/lib/
raise CalledProcessEr
CalledProcessError: Command '('juju', '--show-log', 'config', '-m', 'functional-
Changed in juju: | |
importance: | Medium → High |
Changed in juju: | |
assignee: | nobody → Horacio Durán (hduran-8) |
status: | Triaged → In Progress |
Changed in juju: | |
assignee: | Horacio Durán (hduran-8) → John A Meinel (jameinel) |
This issue happens 50% of the time is restore-backup testing.