-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.0
Description of problem:
Network LB leak after HCP deletion with 4.17 rc build
Version-Release number of selected component (if applicable):
4.17.z
How reproducible:
always
Steps to Reproduce:
1.Create a HCP cluster with 4.17 rc version
2.Wait for cluster ready
3.Wait for some minutes after operators are ready(Know issue: some operators can't be ready: OSD-25117. I wait for 20-30 minutes)
4.Delete cluster
Actual results:
The Network LB is not deleted after cluster deleted
Expected results:
It should be deleted after cluster deleted
Additional info:
The Tag of LB
| Key | Value |
|---|---|
| api.openshift.com/environment | staging |
| api.openshift.com/id | 2dio0buq5aa5qg2ntvg4okslrnac04fk |
| api.openshift.com/legal-entity-id | 1jlfDskrR39egznAq3T18Ul0Xxv |
| api.openshift.com/name | rosacli-ci-o4xu |
| kubernetes.io/cluster/2dio0buq5aa5qg2ntvg4okslrnac04fk | owned |
| kubernetes.io/service-name | openshift-ingress/router-default |
| qe-managed | true |
| red-hat-clustertype | rosa |
| red-hat-managed | true |
| test-tag | tagvalue |
- duplicates
-
-
- Closed
-
-
-
- Closed
-
- links to
-
RHEA-2024:6122
OpenShift Container Platform 4.18.z bug fix update
