This bug is to track to backport to OCS 4.4.x release.
@Elad Can we please target this for the next 4.4.x release. The PR is already merged.
(In reply to Anmol Sachan from comment #3) > @Elad Can we please target this for the next 4.4.x release. The PR is > already merged. In order to mark a bug MODIFIED, you need the downstream/backport PR. https://github.com/openshift/rook/pull/76 This is the d/s 4.4 PR. But it should not have been merged yet, because: 1) This BZ is not fully acked yet (only has devel-ack) 2) This BZ is not targeted for 4.4.1, and should only be merged after 4.4.1 is released. (To avoid including this PR without consent, in the unikely case that we need to respin a build for 4.4.1...) Additionally, using the Target release field is not correct at this stage. We use the internal whiteboard field to propose and approve the BZ for a certain z-stream release. After being fully acked, the target release field will be filled automatically. Let's hope we don't need to respin 4.4.1, since in this case we would need to revert the PR from the branch.
cancelling my needinfo since the PR was merged
canceling my needinfo since the PR was merged
pr needs to be reverted from the 4.4 branch until 4.4.1 is released https://github.com/openshift/rook/pull/78 revert PR
Moving back to POST as this was the revert. Will need to apply this patch again after 4.4.1 has been released.
@Anmol: 4.4.1 is GA now, so we can reapply the patch to 4.4.z branch so that it can be included in 4.4.2
(In reply to Mudit Agarwal from comment #13) > @Anmol: 4.4.1 is GA now, so we can reapply the patch to 4.4.z branch so that > it can be included in 4.4.2 @Anmol, please hold on the backport because we have decided to ship OCS 4.4.2 only with the proposed CVEs. This should be backported when we open the check-ins for 4.4.3
Removing needinfo as the bug is already targeted to 4.4.3