Bug 1746869

Summary: Deleting Network(VPC) in AWS directly doesn't delete some subresources in CFME
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: ProvidersAssignee: Daniel Berger <dberger>
Status: CLOSED WORKSFORME QA Contact: Matouš Mojžíš <mmojzis>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.11.0CC: dmetzger, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: 5.11.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-24 18:45:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1822318    

Description Matouš Mojžíš 2019-08-29 12:05:18 UTC
Description of problem:


Version-Release number of selected component (if applicable):
5.11.0.21

How reproducible:
Always

Steps to Reproduce:
1. Create VPC in AWS directly
2. Associate some subresources to it like subnets and so on.
3. Delete that VPC in AWS directly

Actual results:
When VPC is deleted in AWS all it's associated subresources are deleted as well.
For example associated subnets are deleted in CFME.
Route Tables(Network Routers) are not deleted until manual refresh is triggered.

Expected results:


Additional info:

Comment 2 Daniel Berger 2020-04-24 15:25:36 UTC
I was unable to reproduce this locally on master. I created a VPC, 2 routers, and 2 subnets. I associated both subnets to the same router, leaving the other one unassociated to see if that had any significance.

I deleted the VPC on the AWS console, waited a minute and, without performing a manual refresh, saw that all associated resources - including route tables - had been deleted.

I will double check with a 5.11.0 appliance to see if something was fixed but not backported.

Comment 4 Daniel Berger 2020-04-24 17:13:26 UTC
I tested with a 5.11.0.x appliance, but was still unable to replicate the behavior reported. When I deleted the VPC, the VPC, the subnets and network routers were all deleted without a manual refresh.

Comment 5 Daniel Berger 2020-04-24 18:45:26 UTC
Matous, can you provide an environment