juju run doesn't work with subordinate units
Bug #1286613 reported by
Kapil Thangavelu
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Marco Ceppi |
Bug Description
i was trying to use juju run to debug current settings for a subordinate unit ala
$ juju run --unit=agent/0 "relation-ids ceilometer-service"
ERROR agent/0 is not a principal unit
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: run subordinate |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
milestone: | none → 1.21-alpha2 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
If we're being explicit about which unit we want to target.. i say just let the user do it.. --all can/should nanny filter subordinates, but if a user is specifically interested in running something on a subordinate i don't see the reason not to let them.