Description of problem (please be detailed as possible and provide log snippests): The snapshot PR (https://github.com/topolvm/topolvm/pull/463)has been merged in the upstream topolvm project. We now need to update the downstream release-4.11 branch with the final code changes. Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? The upstream snapshot PR changed the LogicalVolume CRD which will prevent upgrades if not updated in the downstream branch. 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? 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: Expected results: Additional info:
The red-hat-storage/topolvm release-4.11 branch is not synced to the latest upstream main . This now contains the snapshot and clone feature code.
@nibalach Now that the sync was done but build is failed with the feature, what do I do with the status?
(In reply to Shay Rozen from comment #5) > @nibalach Now that the sync was done but build is failed with the > feature, what do I do with the status? Can we mark this dependent on https://bugzilla.redhat.com/show_bug.cgi?id=2103818 and verify post that?
as 4.11.0-110 is working moving 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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix 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/RHSA-2022:6156