Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.12.0
-
None
-
Critical
-
Proposed
-
False
-
Description
Description of problem:
always failed to destroy cluster when using Network Load Balancer, the error logs as below 11-16 13:09:52.486 level=debug msg=unrecognized elastic load balancing resource type listener arn=arn:aws:elasticloadbalancing:us-east-2:301721915996:listener/net/a9de3b7b76c0f433e9197c917bdc9d82/7282e638375263d3/e0483a4307b5cda7 11-16 13:09:52.486 level=debug msg=unrecognized elastic load balancing resource type listener arn=arn:aws:elasticloadbalancing:us-east-2:301721915996:listener/net/a9de3b7b76c0f433e9197c917bdc9d82/7282e638375263d3/77cecece1e7abe9d 11-16 13:09:52.486 level=debug msg=search for matching resources by tag in us-east-2 matching aws.Filter{"kubernetes.io/cluster/hongli-nlb-vk7pd":"owned"} 11-16 13:09:52.486 level=debug msg=search for matching resources by tag in us-east-2 matching aws.Filter{"openshiftClusterID":"44ac912f-2639-45f8-90d9-cf27099d78ac"}
Version-Release number of selected component (if applicable):
4.12.0-0.nightly-2022-11-10-033725
How reproducible:
100%
Steps to Reproduce:
1. create IPI AWS cluster and enable ingress to use Network LB service 2. destroy the cluster
Actual results:
1. see message in the log: unrecognized elastic load balancing resource type listener 2. the destroy job is timeout and failed
Expected results:
destroy cluster successfully.
Additional info:
1. It looks related to "https://github.com/openshift/kubernetes/pull/1412". before the PR merge we didn't find the issue. I tested 4.12.0-0.nightly-2022-11-07-181244 and it works well. 2. we also observed the issue before "https://github.com/openshift/kubernetes/pull/1405" merged which revert "tag AWS security group at creation".