Description of problem: All kubevirt CRDs changed names between CNV 2.3 and CNV 2.4 The NMO moved from "kubevirt.io" to "nodemaintenances.kubevirt.io" (the kind stayed as "NodeMaintenance"). OCP 4.5 was updated to support "nodemaintenances.kubevirt.io" but talking to Dan K, it should not be assumed that CNV 2.3 is only supported on OCP 4.4. Therefore OCP >= 4.5 should check for both the old and new CRD names. Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 100% Steps to Reproduce: 1. Install CNV 2.3 onto OCP 4.5 2. Look for the node maintenance button 3. Actual results: Button not displayed Expected results: Button is displayed Additional info:
Unfortunately there was no capacity this sprint to do this. Moving to upcoming.
Actually we can remove TestBlocker since workaround is to install CNV 2.4
Hey Jiri, is this happening in 4.6? Folks coming from CNV will still care about this
*** Bug 1847822 has been marked as a duplicate of this bug. ***
PR is up for 4.6
Checked on ocp 4.6 BM cluster with payload 4.6.0-0.nightly-2020-09-27-075304。 Before install CNV 2.3 on cluster, there is no "Start maintenance" item in node/BMH action/kebab. After install CNV 2.3 on cluster, the "Start maintenance" item shows up in node/BMH action/kebab. The bug is fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196