-
Bug
-
Resolution: Done-Errata
-
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
[OCPBUGS-39097] Network LB leak after HCP deletion with 4.17 rc build
Ying Zhang
added a comment - rhn-support-jiezhao Can it be closed? Verified pass with 4.17 nightly version : 4.17.0-0.nightly-2024-09-11-001421
Ying Zhang
added a comment - - edited Verified pass with 4.17 nightly version : 4.17.0-0.nightly-2024-09-11-001421 We believe that the root cause for this is the same as the root cause of OCPBUGS-37052. There's a fix that was merged and backported.
rhn-support-yingzhan or rh-ee-dawang can you please verify that this bug is fixed? I verified that the latest nightly build does include the fix that was not part of rc1 or rc2
Demethria Ramseur
added a comment - rhn-support-jiezhao rhn-support-yingzhan Is this still an issue. If yes, please provide additional details (dump) as requested to move the troubleshooting forward.
Demethria Ramseur
added a comment - rhn-support-jiezhao rhn-support-yingzhan Is this still an issue. If yes, please provide additional details (dump) as requested to move the troubleshooting forward. Ying Zhang
added a comment - rhn-support-jiezhao can it reproduce on self-managed side? I don't know how to get hypershift dump.Thanks
Ying Zhang
added a comment - rhn-support-jiezhao can it reproduce on self-managed side? I don't know how to get hypershift dump.Thanks 
dandan wang
added a comment - 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 |
dandan wang
added a comment - 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
Thank you rgarcia@redhat.com I set it as Release Blocker = Proposed since it's bad experience for customers from managed side if there is resource leak.
I've tested core HyperShift self-hosted using 4.17 rc1 quay.io/openshift-release-dev/ocp-release:4.17.0-rc.1-multi and as for HyperShift core on AWS, there were no leaking ELBs
rhn-support-yingzhan can you please share a reproducer for this and check the previous comments? Thank you!
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.18.1 bug fix and security update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:6122