Lack of Openstack resources leaves undead service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
New
|
Undecided
|
Unassigned |
Bug Description
My test suite spawned too many instances, causing me to end up with 10 machines. The 10th failed to spin up, and I'm left with a service I cannot destroy and a machine I cannot terminate.
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.0
dns-name: 10.55.63.139
instance-id: e86d2de7-
series: precise
"1":
agent-state: started
agent-version: 1.11.0
dns-name: 10.55.63.126
instance-id: ae1cdf02-
series: precise
[... trim ...]
"10":
agent-
FlavorId:"1", ImageId:
[... trimmed huge hex dump included in status ...]
, SecurityGroupNa
nova.
caused by: Resource limit exeeded at URL https:/
instance-id: pending
series: precise
services:
postgresql:
charm: local:precise/
exposed: false
life: dying
units:
postgresql/0:
machine: "10"