-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.15.0
-
No
-
False
-
Description of problem:
Creating a second kubevirt OCP cluster. VMs are not getting IPs. VM console trying to get ignition file continuously by this link https://ignition-server-clusters-hcp414-96.apps.provider-client.qe.rh-ocs.com/ignition and receiving a GET error.
Version-Release number of selected component (if applicable):
4.15.0-1615
How reproducible:
The problem appeared on multiple clusters and stable in reproduction. Always with creation of the 2nd cluster
Steps to Reproduce:
1. Prepare Host cluster, OCM, Metal LB, CNV 2. Create first Hosted cluster with cmd hcp create cluster kubevirt --name $KUBEVIRT_CLUSTER_NAME --node-pool-replicas=3 --pull-secret $PULL_SECRET --root-volume-size 40 --memory '12Gi' --cores 6 --infra-storage-class-mapping=oc-storagecluster-cephfs/cephfs --image-content-sources=$SOURCES release-image=quay.io/openshift-release-dev/ocp-release@sha256:8c15455fd05b35f9308f2a73a00a33975d43728b393980c676e365be822b6013 3. Wait until 1st cluster is ready, set new KUBEVIRT_CLUSTER_NAME and run same command again
Actual results:
Node-pools are not getting created. Cluster operators console, dns, image-registry, ingress, insights, kube-storage-version-migrator, monitoring, network, node-tuning, openshift-samples, service-ca are not available VMs created but don't have IPs. VM console show Error with GET request when trying to pull ignition file https://ignition-server-clusters-hcp414-96.apps.provider-client.qe.rh-ocs.com/ignition
Expected results:
OCP cluster created
Additional info:
Infra cluster is vsphere
exact steps are noted here -> https://docs.google.com/document/d/1RfDNQi4B3x4kv9PXx2lqGSD2V2UGideTCIXqLYJFg0Y/edit?usp=sharing