Bug 1788708

Summary: GCP leaking networks
Product: OpenShift Container Platform Reporter: Phil Cameron <pcameron>
Component: InstallerAssignee: Jeremiah Stuever <jstuever>
Installer sub component: openshift-installer QA Contact: Yang Yang <yanyang>
Status: CLOSED DEFERRED Docs Contact:
Severity: high    
Priority: unspecified CC: calfonso, jstuever, scuppett, wking
Version: 4.2.0   
Target Milestone: ---   
Target Release: 4.4.0   
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-02-07 16:57:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1742227, 1793627    
Bug Blocks:    

Description Phil Cameron 2020-01-07 21:24:37 UTC 
Description of problem: GCP leaking networks running ci tests
pull-ci-openshift-cluster-network-operator-master-e2e-gcp #485
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/439/pull-ci-openshift-cluster-network-operator-master-e2e-gcp/485

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 1 W. Trevor King 2020-01-07 21:45:05 UTC 
Might be related to the http-health-checks leak, which should have been fixed via [1], but which has not been backported to 4.2.

[1]: https://github.com/openshift/installer/pull/2387
Comment 2 Stephen Cuppett 2020-01-07 23:43:40 UTC 
Setting to 4.4.0 for investigation of active development branch. 

If the case, we should close this one as CLOSED/CURRENTRELEASE or similar and then clone a backport to 4.2.z
Comment 7 Jeremiah Stuever 2020-01-22 20:34:20 UTC 
This is in part due to bugs 1742227 and 1793627.
Comment 8 Jeremiah Stuever 2020-02-07 16:57:23 UTC 
This appears to have been due 1742227[1] where cluster owned instances were not being deleted due to not containing INFRA_ID in their name. Because we were leaking instances, we were leaking the associated subnets and networks.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1742227