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
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
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
This is in part due to bugs 1742227 and 1793627.
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