juju run gets 'Permission denied (publickey)' in models other than the controller model
Bug #1559233 reported by
Casey Marshall
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
If I create models, `juju run` doesn't work on services deployed into those models. `juju run` only works in the controller model.
This is with Juju 2.0-beta3 built from master @ 764671a8ba9b70f
Steps to reproduce:
$ juju bootstrap dev lxd --upload-tools
...
$ juju deploy wordpress
$ juju deploy mysql
$ juju create-model blog
$ juju deploy wordpress
$ juju deploy mysql
...
$ juju run -m dev --all ps
[works]
$ juju run -m blog --all 'ps'
- MachineId: "0"
ReturnCode: 255
Stderr: "Permission denied (publickey).\r\n"
Stdout: ""
- MachineId: "1"
ReturnCode: 255
Stderr: "Permission denied (publickey).\r\n"
Stdout: ""
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → 2.0-beta3 |
| tags: | added: juju-release-support |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| tags: | added: 2.0-count |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta3 → none |
| milestone: | none → 2.0-beta3 |
To post a comment you must log in.
This has been fixed in the admin-controlle