-
Bug
-
Resolution: Done-Errata
-
Blocker
-
None
-
ACM 2.9.4
-
None
Description of problem:
Submariner cloud-prepare fails when there is an existing VPC that was not provisioned during the initial installation of OpenShift
Version-Release number of selected component (if applicable):
ACM cluster info:
OpenShift 4.14.25 on AWS
ACM 2.9.4
submariner 0.16.0
AWS
Downstream managed OCP cluster info:
OpenShift 4.14.16 on AWS
ODF 4.14.8
How reproducible:
Always
Steps to Reproduce:
1. Label an existing worker node with the following:
oc label node submariner.io/gateway=true`
2. Deploy submariner following the docs
Actual results:
When deploying the submariner gateway node, the deployment fails with the following error:
SubmarinerConfigController reconciliation failed: unable to retrieve the VPC ID: VPC uselab008-5vm8d-vpc not found
Expected results:
Submariner should deploy with an existing VPC that was created prior to the installation of OpenShift
Additional info:
The initial deployment of these clusters uses an existing AWS ec2 VPC that is not provisioned at installation time. The customer pre-provisions the VPC due to their security policy. The VPC name is not what submariner cloud-prepare expects and the cloud-prepare fails to deploy the gateway node.
- links to
-
RHBA-2024:139411 Red Hat Advanced Cluster Management 2.9.4 submariner-addon hotfix