-
Bug
-
Resolution: Unresolved
-
Major
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
Proposed
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
Whenever the annotation hypershift.openshift.io/aws-load-balancer-subnets is set on a HostedCluster (the default in rosa) on a 3-zone management cluster, the AWS vpc endpoint (private link) fails to be created on a hosted cluster that uses 3 zones for its nodes.
Version-Release number of selected component (if applicable):
4.20.0 latest nightly
How reproducible:
always
Steps to Reproduce:
1. Create a management cluster with machines in 3 zones (can be hosted cluster)
2. Create a PublicAndPrivate HostedCluster with nodepools in 3 zones and annotate it with hypershift.openshift.io/aws-load-balancer-subnets pointing to 2 of the subnets of the management cluster.
3. Wait for the HostedCluster to come up
Actual results:
The HostedCluster never finishes provisioning because its VPC endpoint cannot be created.
Expected results:
The HostedCluster is created normally
Additional info:
Regression introduced by https://github.com/openshift/hypershift/pull/3946
- depends on
-
-
- Verified
-
- links to
