-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.14.z
-
No
-
False
-
Description of problem:
After finishing a hypershift scale job in staging that creates and deletes 74 HC(successfully), there are a few LBs left behind or left uncleaned in MC AWS account that could affect the quota per MC. Especially we are very limited on RulesPerSecurityGroup and an MC capacity is dependent on this resource, leaving stale or orphan resource would affect the cluster creation
Version-Release number of selected component (if applicable):
4.14.0
How reproducible:
Most of time during scale job
Steps to Reproduce:
1. Create and delete a bunch of HC
2. After deletion check the Management cluster LB/Security Group for any leaks
3.
Actual results:
It leaves some AWS SG rules behind and affects the quota
Expected results:
It should clean up all created AWS resources after HC deletion including SG rules
Additional info: