does not clean up security groups

Bug #1643974 reported by Jeff Pihach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Undecided
Richard Harding

Bug Description

Using 2.0.0-trusty-amd64

When destroying a controller I got the following error message:

ERROR cannot determine security groups to delete: cannot retrieve instance information from aws to delete security groups: 503 Service Unavailable

Going into the aws console I see I have over 150 security groups so it doesn't look like Juju is cleaning them up.

Changed in juju:
status: New → Triaged
importance: Undecided → High
importance: High → Critical
milestone: none → 2.1.0
Changed in juju:
assignee: nobody → Richard Harding (rharding)
Revision history for this message
Martin Packman (gz) wrote :

Have you got any additional information on the circumstances this appeared in, or subsequent occurrences?

As seen in CI testing, in normal operation juju does correctly delete security groups in ec2:

<http://reports.vapour.ws/releases/4648/job/aws-native-deploy-bundle/attempt/690>

However cloud outage and other test problems can result in resource leakage, so we do have a fallback script that goes around deleting old security groups as well.

Revision history for this message
Jeff Pihach (hatch) wrote :

I don't, it is likely a spurious issue and one that over the past few years has created and left quite a few

Revision history for this message
Anastasia (anastasia-macmood) wrote :

As per comment # 1, we cannot reproduce the issue without a scenario.
Our testing shows that ec2 security groups are deleted.

Changed in juju:
status: Triaged → Incomplete
milestone: 2.1.0 → none
Changed in juju:
importance: Critical → Undecided
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.