The following run targets are not valid: "" is not a valid unit name

Bug #1641163 reported by Ryan Beisner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Wait Plugin
Fix Committed
Undecided
Stuart Bishop

Bug Description

After the following commits on Nov 10, OpenStack Charm CI's juju-wait is failing on subordinates, and when juju-waiting after a bootstrap, before applications are deployed.

The full juju-wait debug output is:
INFO:root:All units idle since 2016-11-11 15:43:59.230940Z ()
ERROR:root:error: The following run targets are not valid:
  "" is not a valid unit name
ERROR:root:juju run --format=yaml --unit -- is-leader --format=json failed: 2

https://git.launchpad.net/juju-wait/commit/?id=783cc92361b3a95a665a6f7489937c927cd91628

https://git.launchpad.net/juju-wait/commit/?id=1ec3d231e9282b3fad145cd8fab48818ce1075d5

https://git.launchpad.net/juju-wait/commit/?id=8741cb05a23ea8567f7f189aacd031822cc9783d

Tags: uosci
Revision history for this message
Ryan Beisner (1chb1n) wrote :

It appears that juju_run_many() is blindly juju running without checking that there are indeed units.

description: updated
Ryan Beisner (1chb1n)
description: updated
Stuart Bishop (stub)
Changed in juju-wait:
status: New → Fix Committed
assignee: nobody → Stuart Bishop (stub)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.