-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.15.z
-
None
-
Important
-
No
-
False
-
Description of problem:
OCP 4.15.16 deployment on a Bare-metal server failed without the provisioning network.
Version-Release number of selected component (if applicable):
How reproducible:
Everytime - without the provisioning network
Steps to Reproduce:
1. applying install config 2. Cluster creation reports: Dependency failed for Ironic baremetal deployment service. [core@localhost ~]$ journalctl -b -f -u release-image.service -u ironic Jun 24 07:09:30 localhost.localdomain systemd[1]: Starting Download the OpenShift Release Image... Jun 24 07:09:30 localhost.localdomain release-image-download.sh[1831]: Pulling quay.io/openshift-release-dev/ocp-release@sha256:4bdebcbc36c2b4c383b70cf5e23b168f8bf445eba42fc8f331643608a60398e8... Jun 24 07:28:38 localhost.localdomain release-image-download.sh[1926]: f0c2c176e57ffcc1582fc91246fca2361b93cf59fc0767eac6ff08f8b94262be Jun 24 07:28:38 localhost.localdomain podman[1926]: 2024-06-24 07:09:30.663071093 +0000 UTC m=+0.051137749 image pull quay.io/openshift-release-dev/ocp-release@sha256:4bdebcbc36c2b4c383b70cf5e23b168f8bf445eba42fc8f331643608a60398e8 Jun 24 07:28:39 localhost.localdomain systemd[1]: Finished Download the OpenShift Release Image. Jun 24 07:33:44 localhost.localdomain systemd[1]: Dependency failed for Ironic baremetal deployment service. Jun 24 07:33:44 localhost.localdomain systemd[1]: ironic.service: Job ironic.service/start failed with result 'dependency'. 3. Cluster creation fails with: failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failure applying terraform for "masters" stage: error applying Terraform configs: failed to apply Terraform: error(BaremetalIronicAPITimeout) from Infrastructure Provider: Unable to the reach provisioning service. This failure can be caused by incorrect network/proxy settings, inability to download the machine operating system images, or other misconfiguration. Please check access to the bootstrap host, and for any failing services.
Actual results:
Expected results:
Additional info
bootkube.service logs gets stuck at:
Jun 24 08:40:01 api.ipi-cert-cm7.dcrhel.com bootkube.sh[34164]: Skipped "secret-loadbalancer-serving-signer.yaml" secrets.v1./loadbalancer-serving-signer -n openshift-kube-apiserver-operator as it already exists
Jun 24 08:40:02 api.ipi-cert-cm7.dcrhel.com cluster-bootstrap[34187]: Skipped "secret-localhost-serving-signer.yaml" secrets.v1./localhost-serving-signer -n openshift-kube-apiserver-operator as it already exists
Jun 24 08:40:02 api.ipi-cert-cm7.dcrhel.com bootkube.sh[34164]: Skipped "secret-localhost-serving-signer.yaml" secrets.v1./localhost-serving-signer -n openshift-kube-apiserver-operator as it already exists
Jun 24 08:40:02 api.ipi-cert-cm7.dcrhel.com cluster-bootstrap[34187]: Skipped "secret-service-network-serving-signer.yaml" secrets.v1./service-network-serving-signer -n openshift-kube-apiserver-operator as it already exists
Jun 24 08:40:02 api.ipi-cert-cm7.dcrhel.com bootkube.sh[34164]: Skipped "secret-service-network-serving-signer.yaml" secrets.v1./service-network-serving-signer -n openshift-kube-apiserver-operator as it already exists
- duplicates
-
OCPBUGS-34493 ironic.service fails to start on bootstrap node when provisioning network is disabled
- Closed
- impacts account
-
OCPBUGS-24648 OCP 4.15 nightly deployment on a bare-metal server without using the provisioning network is stuck during deployment.
- Verified