Mudit, Rakshith, The decision to move this bug to 4.14.0 in comment #34 was based on the assumption that the issue hit in bug 2184748 is a separate one. But ever since then, bug 2184748 got closed as a DUP of this one, so that assumption turned out to be wrong. Since we are able to reproduce, as mentioned by Aman in comment 30, and since the testing in 4.13 hasn't gained much momentum to date, we should keep this bug in 4.13.0 and not move it out.
Elad, Bug #2184748 is duped to #2185953 and not this one. #2185953 is already proposed as a blocker for 4.13 Please correct me if I am missing anything here.
You are right. I misread the bug number. Please disregard
Just by reading comment #42, this sounds like https://github.com/kubernetes/kubernetes/issues/114207 It has been fixed in recent upstream releases, in 4.12 it should be fixed by https://github.com/openshift/kubernetes/pull/1582
Jan, I guess Aman is using 4.13 here (comment #41) in which case we should not see this issue.
4.13 is quite similar to 4.12 here: - The bug was fixed in 1.26.5 upstream: https://github.com/kubernetes/kubernetes/issues/114207#issuecomment-1535623925 - 4.13 has 1.26.3 and update to 1.26.5 has been just opened: https://github.com/openshift/kubernetes/pull/1586 It will take some time to merge & promote it in a OCP z-stream release.
Thanks Jan. Aman, https://github.com/openshift/kubernetes/pull/1586 is merged in OCP 4.13. So, we should retest it now. Meanwhile, this is not a TP blocker. Hence moving it out of 4.13
(In reply to Mudit Agarwal from comment #55) > Thanks Jan. > > Aman, https://github.com/openshift/kubernetes/pull/1586 is merged in OCP > 4.13. > So, we should retest it now. > > Meanwhile, this is not a TP blocker. Hence moving it out of 4.13 Ack, noted!
It looks like this is getting addressed by a fix in OpenShift, not in the Ceph-CSI driver. Adding the "Tracking" keyword to indicate no code changes in the selected component.
Please do not move the bugs to ON_QA without the acks. Move it to MODIFIED if it is already fixed and ask for the acks.
(In reply to Mudit Agarwal from comment #62) > Please do not move the bugs to ON_QA without the acks. Move it to MODIFIED > if it is already fixed and ask for the acks. Sorry, I probably misunderstood how OCP tracking bugs are handled then. There is no ODF build needed for this, it is purely an OpenShift fix. The OpenShift bugs are closed, so I assume a build of OCP is available that can be used for testing. Even without the acks the fix is included in recent/new deployments of ODF, and ready for QE to test.
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.15.0 security, enhancement, & 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/RHSA-2024:1383