bootstrap failed due to failure to create security group

Now that machine is broken,

ubuntu@juju-hp-machine-0:~$ tail -f /var/log/juju/machine-0.log
2014-02-17 05:15:37 ERROR juju.provisioner provisioner_task.go:403 cannot start instance for machine "2": cannot set up groups: failed to create a security group with name: juju-hp
caused by: request (https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/os-security-groups) returned unexpected status: 500; error info: {"computeFault": {"message": "The server has either erred or is incapable of performing the requested operation.", "code": 500}}
2014-02-17 05:15:39 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "3566551": no instances found
2014-02-17 05:15:49 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-02-17 05:15:56 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "3566551": no instances found
2014-02-17 05:16:06 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-02-17 05:16:15 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "3566551": no instances found
2014-02-17 05:16:25 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-02-17 05:16:38 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "3566551": no instances found
2014-02-17 05:16:48 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-02-17 05:17:09 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "3566551": no instances found

I have also seen this deploying charms to a local provider.

2014-03-04 19:02:37 INFO juju.worker.machiner machiner.go:88 setting addresses for machine-0 to ["10.0.1.136" "10.0.3.1" "192.168.122.1" "fe80::924c:e5ff:fe44:bb93" "fe80::c43b:4cff:fe8f:7a5d"]
2014-03-04 19:02:37 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
2014-03-04 19:02:37 ERROR juju runner.go:220 worker: exited "environ-provisioner": no state server machines with addresses found
2014-03-04 19:03:19 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:21 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:24 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:24 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:25 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:26 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:26 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:29 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:30 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:30 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:31 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:35 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:38 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found
2014-03-04 19:03:43 WARNING juju.worker.instanceupdater updater.go:231 cannot get instance info for instance "": no instances found

Dave, Is this bug a dupe of bug 1227574 [destroy-env on openstack should remove sec groups] or bug 1217595 [security groups reused without ensuring validity]?

I regularly purge secgroups on hp and canonistack since juju doesn't delete them (allowing me to exceed the resource limits or get a group that old rules). As I re-read this bug description, I think the proper title is: juju failed to create secgroup on bootstrap. The charm is irrelevant in this case. I think the underlying issue is that juju mis-manages security groups.

I agree, the correct title is something along the lines of "bootstrap
failed due to failure to create security group"

On Wed, Mar 5, 2014 at 6:55 AM, Curtis Hovey <email address hidden> wrote:
> Dave, Is this bug a dupe of bug 1227574 [destroy-env on openstack should
> remove sec groups] or bug 1217595 [security groups reused without
> ensuring validity]?
>
> I regularly purge secgroups on hp and canonistack since juju doesn't
> delete them (allowing me to exceed the resource limits or get a group
> that old rules). As I re-read this bug description, I think the proper
> title is: juju failed to create secgroup on bootstrap. The charm is
> irrelevant in this case. I think the underlying issue is that juju mis-
> manages security groups.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1280953
>
> Title:
> juju cannot deploy the ubuntu charm on hp cloud
>
> Status in juju-core:
> Triaged
>
> Bug description:
> lucky(~) % juju deploy ubuntu -v
> verbose is deprecated with the current meaning, use show-log
> 2014-02-17 05:15:26 INFO juju api.go:231 connecting to API addresses: [15.185.89.124:17070]
> 2014-02-17 05:15:26 INFO juju apiclient.go:118 state/api: dialing "wss://15.185.89.124:17070/"
> 2014-02-17 05:15:28 INFO juju apiclient.go:128 state/api: connection established
> Added charm "cs:precise/ubuntu-4" to the environment.
> 2014-02-17 05:15:31 INFO juju.cmd supercommand.go:300 command finished
> lucky(~) % juju status
> environment: hp
> machines:
> "0":
> agent-state: started
> agent-version: 1.17.3.1
> dns-name: 15.185.89.124
> instance-id: "3566551"
> instance-state: ACTIVE
> series: precise
> hardware: arch=amd64 cpu-cores=1 mem=1024M root-disk=30720M
> "2":
> agent-state-info: '(error: cannot set up groups: failed to create a security group
> with name: juju-hp
>
> caused by: request (https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/os-security-groups)
> returned unexpected status: 500; error info: {"computeFault": {"message": "The
> server has either erred or is incapable of performing the requested operation.",
> "code": 500}})'
> instance-id: pending
> series: precise
> services:
> ubuntu:
> charm: cs:precise/ubuntu-4
> exposed: false
> units:
> ubuntu/0:
> agent-state: pending
> machine: "2"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1280953/+subscriptions

changing title, per comments #3 & #4