-
Bug
-
Resolution: Done-Errata
-
Blocker
-
CNV v4.19.0, CNV v4.19.1
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
CNV v4.19.1.rhel9-18
-
-
Critical
-
Customer Facing, QE Confirmed, Customer Reported
-
None
Description of problem:
After completing the upgrade of OCP to 4.19, during the CNV upgrade to 4.19, the virt-handler pods on several nodes are crashing due to invalid memory address or nil pointer dereference. logs provided.
Version-Release number of selected component (if applicable):
OCP 4.19.1 CNV 4.19.1
How reproducible:
occurred on cnv2.engineering.redhat.com upgrade
Steps to Reproduce:
1. Upgrade OCP from 4.18 to 4.19 2. Upgrade CNV from 4.18 to 4.19 3. Watch the virt-handler pods in CrashloopBackoff
Actual results:
virt-handler pods are crashing due to nil pointer deference. the upgrade is stuck due to that.
Expected results:
all virt-handlers should come up ready and upgrade should continue
Additional info:
the affected nodes probably ran VMs migrations on them during the upgrade.
- is depended on by
-
CNV-64426 Upgrade path from CNV v4.18 to CNV v4.19 needs to be re-enabled
-
- Closed
-
- is related to
-
CNV-64416 [CLOSED LOOP for] virt-handlers are crashing during CNV upgrade to 4.19
-
- New
-
- links to
-
RHEA-2025:151115 OpenShift Virtualization 4.19.1 Images