deployer sometimes fails with a unit status not found error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth | ||
1.24 |
Fix Released
|
High
|
Ian Booth |
Bug Description
Seems to be intermittent.
As reported in http://
2015-05-03 14:25:57 [DEBUG] deployer.import: Waiting for deploy delay
2015-05-03 14:26:12 [DEBUG] deployer.import: Adding units...
Traceback (most recent call last):
File "/usr/bin/
load_
File "/usr/lib/
run()
File "/usr/lib/
importer.
File "/usr/lib/
self.
File "/usr/lib/
env_status = self.env.status()
File "/usr/lib/
return self.client.
File "/usr/lib/
return StatusTranslato
File "/usr/lib/
change_set = watch.next()
File "/usr/lib/
'Id': self.watcher_id})
File "/usr/lib/
raise EnvError(result)
jujuclient.
{ u'Error': u'status for key "u#python-django/0" not found',
u'ErrorCode': u'not found',
u'RequestId': 1,
u'Response': { }}
Status snippet:
python-django:
charm: cs:trusty/
exposed: false
service-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 May 2015 14:25:50 UTC
units:
python-
current: unknown
message: Waiting for agent initialization to finish
since: 03 May 2015 14:25:50 UTC
current: allocating
since: 03 May 2015 14:25:50 UTC
machine: 2/lxc/0
Changed in juju-core: | |
status: | Triaged → In Progress |
summary: |
- depployer sometimes fails with a unit status not found error + deployer sometimes fails with a unit status not found error |
tags: | added: intermittent-failure |
tags: | added: landscape |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: kanban-cross-team |
Marking down to High because the last 2 CI runs passed. There's still potentially an intermittent issue though which needs to be investigated.