-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14.z
-
Critical
-
No
-
False
-
Description of problem:
Customer has provided subnets to deploy the cluster into, however the NLB is deploying to other subnets. This eventually results in the cluster being unusable by the customer.
Version-Release number of selected component (if applicable):
4.14.13
How reproducible:
This seems to be occurring frequently with customers who have multiple subnets within a shared VPC.
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
I'm filing this as a separate bug from the related card as the related card is specific to Management Clusters which do NOT have, as far as I'm aware, multiple additional subnets within shared VPCs. If this is determined to be the same issue I'm more than happy to have this one or the other closed and merged. I also just was informed of the presence of OCPBUGS-30750 which I've also linked, which relates to CLBs, and may be the same root cause. Again, if we determine this to be the same issue I'm more than happy to have this issue closed and merged with one of the other related ones and apologize for the additional noise.
- relates to
-
OCPBUGS-30260 Correctly handle HCP subnet tagging for management clusters to not break cloud-provider-aws subnet selection
- POST
-
OCPBUGS-30750 Cluster Load Balancers Unable to Find Suitable Subnets
- Closed