juju status backtrace: Machine provider information missing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
Using juju 0.6.0.1+
Deployed a service but the cloud instance didn't start:
$ euca-describe-
RESERVATION r-3wg6u15l 4ea76ff134b4488
INSTANCE i-0000228d ami-0000016b juju-shared-
juju status shows a backtrace in this situation:
$ juju status
2013-01-16 13:32:16,818 WARNING S3 API calls not using secure transport
2013-01-16 13:32:16,818 INFO Connecting to environment...
2013-01-16 13:32:18,612 INFO Connected to environment.
2013-01-16 13:32:19,631 ERROR Machine provider information missing: machine 3
Traceback (most recent call last):
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
returnValue
File "/usr/lib/
raise _DefGen_Return(val)
_DefGen_Return
machines:
0:
agent-state: running
dns-name: 10.55.63.22
instance-id: 39c02c50-
instance-state: running
3:
instance-id: 00948aa7-
services:
landscape-devenv:
charm: local:precise/
relations: {}
units:
landscape
machine: 3
2013-01-16 13:32:19,634 INFO 'status' command finished successfully
Ideally it should show the error state at the top, under "3:". Probably a "instance-state: error".
Changed in juju: | |
importance: | Undecided → Low |
status: | New → Triaged |
This should be Won't Fix.