provisioning agent gets confused when machines are terminated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Undecided
|
Unassigned | ||
juju (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned |
Bug Description
Have noticed this that sometimes when I terminate a machine the provisioning agent starts repeatedly logging this in debug-log:
2011-09-28 19:53:38,420 provision:ec2: juju.agents.
Traceback (most recent call last):
File "/usr/lib/
machine_
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
machine_
File "/usr/lib/
result = g.send(result)
File "/usr/lib/
raise MachineStateNot
MachineStateNot
This is on the latest packages from PPA
$ apt-cache policy juju
juju:
Installed: 0.5+bzr363-
Candidate: 0.5+bzr363-
Version table:
*** 0.5+bzr363-
500 http://
100 /var/lib/
Changed in juju: | |
milestone: | none → florence |
assignee: | nobody → Jim Baker (jimbaker) |
Terminate a machine how?.. with the juju remove-machine api.. or ec2
destroy-instance api ?
Excerpts from Clint Byrum's message of Wed Sep 28 23:59:41 UTC 2011:
> Public bug reported:
>
> Have noticed this that sometimes when I terminate a machine the
> provisioning agent starts repeatedly logging this in debug-log:
>