cannot bootstrap on openstack provider: Multiple security_group matches found for name 'XYZ', use an ID to be more specific.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Unassigned | ||
OpenStack Charm Test Infra |
Invalid
|
High
|
Unassigned | ||
juju-core |
Fix Released
|
Undecided
|
Unassigned | ||
1.25 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Now observed with Ubuntu OpenStack Kilo as the undercloud, with juju 1.25.0 and juju 1.25.1(proposed) and the juju openstack provider.
This blocks deploy/test automation where iterative bootstrap/
2015-11-24 14:26:47 ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: cannot start bootstrap instance: cannot run instance: failed to run a server with nova.RunServerOpts{ ...
caused by: request (http://
# juju bootstrap --debug output:
http://
--- original description ---
On HP cloud, I encounter a case where I end up with the juju-hp-global security group defined twice.
I use:
firewall-mode: global
use-
in my environments.yaml file.
This is not reproducible at will but more likely to happen when a deployment is already present and I'm running more juju deployer commands to complete a deployment.
juju status also gives some hard to parse hints:
"12":
agent-
FlavorId:
< ~500 lines of: 0x99, 0xb6, 0x7f, 0x14, 0x4d, 0x1b, 0xc7, 0x72, 0xa9, 0x84, 0x2e, 0x98, 0x72, stuff>
SecurityG
nova.
caused by: request (https:/
returned unexpected status: 409; error info: {"conflictingRe
"Multiple security_group matches found for name ''juju-hp-global'', use an ID
to be more specific.", "code": 409}})'
instance-id: pending
series: precise
I would guess that checking the existence of juju-hp-global fails for some unexpected cause (rate limitation, nova transient error) and juju believes the group doesn't exist and create a *new* one.
At that point there are two existing juju-hp-global secgroups and juju can't recover:
$ nova secgroup-list
+------
| Id | Name | Description |
+------
| f9b0e939-
| c37f45d9-
| 32fb3fef-
| d9cf6d0a-
+------
Changed in juju-core: | |
importance: | High → Medium |
milestone: | next-stable → none |
description: | updated |
tags: | added: uosci |
Changed in juju-core: | |
importance: | Medium → High |
milestone: | none → 1.26-beta1 |
tags: | added: repeatability |
tags: | added: charmers |
tags: | added: bug-squad |
Changed in juju-core: | |
milestone: | 1.26-beta1 → 2.0-alpha2 |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.0 |
tags: | removed: hp-cloud |
Changed in juju-core: | |
status: | Triaged → Incomplete |
Changed in juju-core: | |
status: | Incomplete → Invalid |
tags: | added: sts |
Changed in juju: | |
status: | Incomplete → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.2.0 |
assignee: | nobody → Alexis Bruemmer (alexis-bruemmer) |
Changed in charm-test-infra: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in juju-core: | |
milestone: | none → 1.25.11 |
Changed in juju: | |
assignee: | Alexis Bruemmer (alexis-bruemmer) → nobody |
Changed in juju: | |
milestone: | 2.1.0 → 2.1-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in charm-test-infra: | |
status: | Confirmed → Invalid |
Juju CI sees this too. We added a script to purge the env's secgroup after tests to ensure the next use the the env doesn't see the phantom secgroup.