Description of problem (please be detailed as possible and provide log snippests): A bug in the pkg/deploymanager code causes the e2e tests to fail in the ValidateVolumeSnapshotClass function. The error is: Error getting volumesnapshotclass. Err: no kind is registered for the type v1.VolumeSnapshotClass in scheme "pkg/runtime/scheme.go:100" Version of all relevant components (if applicable): release-4.11 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: make e2e-test fails in the release-4.11 branch. Expected results: make e2e-test should pass. Additional info: The fix does not affect the product in any way as the code changes are limited to the e2e test code and deploymanager package.
Approving it for 4.11.2 as the changes are only in the e2e files.
No QE required, no need to attach it to errata as well.
@Nithya - is this bug good to be moved to verified?
(In reply to krishnaram Karthick from comment #8) > @Nithya - is this bug good to be moved to verified? Yes Karthick. I will move it to Verified.
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 (Red Hat OpenShift Data Foundation 4.11.2 Bug Fix Update), 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-2022:6888