juju-check-wait fails when a machine is down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Confirmed
|
Medium
|
Unassigned |
Bug Description
This happened when I was running a manifest.
020-12-02 14:40:02 [INFO] Retrieve the spec's manifest
2020-12-02 14:40:02 [INFO] Running 'mojo run -m manifests/
2020-12-02 14:40:02 [INFO] Checking Juju status
2020-12-02 14:40:02 [INFO] Waiting up to 1800 seconds for environment to become ready (not blocked or in maintenance)
2020-12-02 14:40:03 [ERROR] Unknown error
Traceback (most recent call last):
File "/usr/lib/
args.func(args)
File "/usr/lib/
return method(*args, **kwargs)
File "/usr/lib/
manifest.
File "/usr/lib/
phase_
File "/usr/lib/
timeout=
File "/usr/lib/
if self.ready(): # self.ready() will raise exceptions on error states
File "/usr/lib/
machines_ready = self.machines_
File "/usr/lib/
if not self._check_
KeyError: 'current'
I did a manual juju status, which shows one of my machines as down. nova list shows it in a Shutdown state, so maybe you can reproduce this in a deployed environment by shutting down a machine.
summary: |
- checking status fails when a machine is down + juju-check-wait fails when a machine is down |
Changed in mojo: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Addendum. I've restarted the machine and I'm still getting this even after juju status shows that it is back up.