get_model fails for shared controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-deployer |
Fix Released
|
Undecided
|
Tim Kuhlman |
Bug Description
When running on a shared controller I get the bug:
Traceback (most recent call last):
File "/usr/local/
load_
File "/usr/lib/
run()
File "/usr/lib/
importer.
File "/usr/lib/
self.
File "/usr/lib/
self.client = self.client_
File "/usr/lib/
return connector(
File "/usr/lib/
jhome, data = self.parse_
File "/usr/lib/
model = self.get_
File "/usr/lib/
['juju', 'show-model', '-m', model, '--format=yaml'])
File "/usr/lib/
output = subprocess.
File "/usr/lib/
raise CalledProcessEr
subprocess.
Running 'juju show-model -m laptop:mojo-test' does fail, but running 'juju show-model -m laptop:
"$ juju models
MODEL OWNER STATUS LAST CONNECTION
admin/mojo-test* admin@local available 7 seconds ago
"
The juju user being run as was created with 'juju add-user', granted write to the model and added to the machine above with 'juju register'.
I have tried this with Juju beta15 straight from the xenial repos and with juju beta18 from the devel ppa.
Related branches
- Tim Van Steenburgh (community): Approve
-
Diff: 72 lines (+13/-7)2 files modified.bzrignore (+1/-0)
jujuclient/juju2/connector.py (+12/-7)
Changed in juju-deployer: | |
assignee: | nobody → Tim Kuhlman (timkuhlman) |
Changed in juju-deployer: | |
status: | New → In Progress |
Changed in juju-deployer: | |
status: | In Progress → Fix Committed |
New build in ppa:tvansteenbu rgh/ppa