destroy-env on openstack should remove sec groups

Bug #1227574 reported by Kapil Thangavelu on 2013-09-19
52
This bug affects 9 people
Affects Status Importance Assigned to Milestone
juju-core
High
Abel Deuring

Bug Description

Destroy environment should clean up security groups. The openstack api let's one manipulate groups at runtime unlike the ec2 api (which wants the instances to be terminated before allowing removal of group). There's no reason we should be leaving these behind, especially given the relatively low count of security groups an openstack provider allows.

Related branches

description: updated
John A Meinel (jameinel) wrote :

as noted in the duplicate, this also interacts poorly with bug #1217595 and bug #1226996 in that if security groups are left around, we just use them as they were. Though I would focus on fixing bug #1217595 before this one.

Changed in juju-core:
importance: Undecided → High
status: New → Triaged
Curtis Hovey (sinzui) on 2013-10-14
tags: added: destroy-environment security
Curtis Hovey (sinzui) on 2013-10-15
tags: added: canonical-webops destroy-machine
Marco Ceppi (marcoceppi) wrote :

This continues to be an issue for HP Cloud adoption, given bug #1217595 this creates un-expected results (services being exposed when they weren't explicitly, etc)

Ryan Finnie (fo0bar) on 2014-03-04
tags: added: canonical-is
Curtis Hovey (sinzui) on 2014-03-24
tags: added: charmers ci
Curtis Hovey (sinzui) on 2014-04-11
Changed in juju-core:
milestone: none → 1.19.0
assignee: nobody → Abel Deuring (adeuring)
status: Triaged → Fix Committed
Curtis Hovey (sinzui) on 2014-04-15
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers