[AWS] secgroups not cleaned up after "juju destroy-model"

Bug #1712338 reported by Junien F
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

Hi,

With juju 2.2.2, if you create a model, deploy some units in it, and then destroy the model, the security group of the model is removed, but not the security groups assigned to each machine.

Easy repro :
 - juju bootstrap
 - juju add-model whatever
 - juju deploy cs:ubuntu
 - juju destroy-model whatever

Result : the secgroup juju-${model_uuid} is gone, but the secgroup juju-${model_uuid}-0 is still present.

Expected result : both secgroups are gone.

This was tested in ca-central-1.

Thanks

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

At the same time as addressing this bug, we should also ensure that we log clearly any secgroup manipulation failures as per bug # 1712297.

Changed in juju:
status: New → Triaged
importance: Undecided → High
tags: added: sec-groups
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.