-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17, 4.16.z
Description of problem:
the parameter `--network-type` in the command `hypershift create cluster aws` should support multiple types like Other, Calico, OpenShiftSDN.
But now if you specify it as `OpenShiftSDN` or `Other`, the HC will fail on the initial validation phase.
$ hypershift create cluster aws -h ... --network-type string Enum specifying the cluster SDN provider. Supports either Calico, OVNKubernetes, OpenShiftSDN or Other. (default "OVNKubernetes") $ oc get hc hei-test -A -oyaml ... networking: clusterNetwork: - cidr: 10.132.0.0/14 machineNetwork: - cidr: 10.0.0.0/16 networkType: Other serviceNetwork: - cidr: 172.31.0.0/16 ... - lastTransitionTime: "2024-06-12T14:57:38Z" message: 'ValidConfiguration condition is false: service type OVNSbDb not found' observedGeneration: 3 reason: Blocked status: "False" type: Progressing
Version-Release number of selected component (if applicable):
4.17, 4.16.z
How reproducible:
100%
Steps to Reproduce:
$ hypershift create cluster aws --name=heli-test --pull-secret=/Users/harry/pull-secret --aws-creds=/Users/harry/.aws/credentials --node-pool-replicas=1 --region=us-east-2 --base-domain=qe.devcluster.openshift.com '--annotations=hypershift.openshift.io/cleanup-cloud-resources="true"' --ssh-key=/Users/harry/.ssh/id_rsa.pub --namespace=clusters --release-image=registry.ci.openshift.org/ocp/release@sha256:661df212f08446e32bb051fff76dfa36b11aea7ab217993ea0114cf97435d461 --network-type=Other
Actual results:
$ oc get hc -A NAMESPACE NAME VERSION KUBECONFIG PROGRESS AVAILABLE PROGRESSING MESSAGE clusters heli-test Partial False False ValidConfiguration condition is false: service type OVNSbDb not found
Expected results:
hc could be ready with Other networkType
Additional info:
- blocks
-
-
- Closed
-