-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19.0
-
None
When using OCP 4.19.4 with the ISO created for dev-preview here https://docs.google.com/document/d/1LwBreYsCHu7GdIRZSQ-cmX0v0X43nsWfsjSGUx2aDm0/edit?tab=t.0#heading=h.ehbig09qxngl the installation fails with ingress errors.
Both master-1 and master-2 have their image successfully written to disk but then after reboot they both exhibit the following errors:
Jul 15 01:24:04 master-1 kubenswrapper[14383]: I0715 01:24:04.709147 14383 prober.go:107] "Probe failed" probeType="Startup" pod="openshift-ingress/router-default-6598d778f4-pf7hn" podUID="3689e55f-d798-451d-97ce-51b711185ad8" containerName="router" probeResult="failure" output="HTTP probe failed with statuscode: 500"
The installation gets stuck at 65% and the ingress cluster operator does not proceed:
ingress False True True 18m The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
This happens when using the image built as in the google doc as above, and also when built manually.
- blocks
-
AGENT-1182 OVE ISO 4.19 Dev Preview release
-
- Closed
-
-
OCPBUGS-59741 OVE UI fails to install when using OCP 4.19.4
-
- Closed
-
-
OCPBUGS-59742 OVE UI fails to install when using OCP 4.19.4
-
- Closed
-
- is cloned by
-
OCPBUGS-59741 OVE UI fails to install when using OCP 4.19.4
-
- Closed
-
-
OCPBUGS-59742 OVE UI fails to install when using OCP 4.19.4
-
- Closed
-
- is duplicated by
-
OCPBUGS-59742 OVE UI fails to install when using OCP 4.19.4
-
- Closed
-
- is related to
-
ACM-21309 Nightly images should be signed or served from other registry
-
- Resolved
-
- links to