-
Bug
-
Resolution: Done
-
Major
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
1
-
Moderate
-
None
-
None
-
Rejected
-
NI&D Sprint 276, NI&D Sprint 277
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
The CI test TestAWSLoadBalancerControllerWithCredentialsSecret is currently failing as a flaky CI. We have observed this and decided to file it as a bug.
--- FAIL: TestAWSLoadBalancerControllerWithCredentialsSecret (920.10s) === RUN TestAWSLoadBalancerControllerWithCustomIngressClass operator_test.go:406: Creating test namespace "aws-load-balancer-test-custom-ing" operator_test.go:412: Creating a custom ingress class operator_test.go:422: Creating aws load balancer controller instance with custom ingress class util.go:72: failed to get deployment aws-load-balancer-controller-cluster: deployments.apps "aws-load-balancer-controller-cluster" not found (retrying) util.go:72: failed to get deployment aws-load-balancer-controller-cluster: deployments.apps "aws-load-balancer-controller-cluster" not found (retrying) util.go:72: failed to get deployment aws-load-balancer-controller-cluster: deployments.apps "aws-load-balancer-controller-cluster" not found (retrying)
aws-load-balancer-pre-install CI step creates the necessary CredentialsRequest to provision AWS credentials secret for the controller. However the secret is not provisioned due to missing target namespace (aws-load-balancer-operator) which is created later during the CI installation.
A related fix for the operator CredentialsRequest was merged here. Unlike the operator fix which relied on ALBO doing the self provisioning during the startup, the controller fix should be added to the e2e code (before tests start to run).
- links to
- mentioned on
(6 mentioned on)
