Description of problem:
Following on the Bugzilla 1952819, Some customers are querying to get the fix backported to the EUS version 4.6.z
This Bug has been rated with a High severity, and according to the Maintenance support description, it may be eligible to be backported to the version 4.6 and 4.7
"During the Maintenance Support phase, qualified Critical and Important Security Advisories (RHSAs) and Urgent and Selected High Priority Bug Fix Advisories (RHBAs) may be released as they become available. Other Bug Fix (and Enhancement (RHEA) Advisories may be released at Red Hat’s discretion, but should not be expected."
Version-Release number of selected component (if applicable):
Even if a KCS has been created for this bug, some customers are wondering if the fix will be backported to 4.6.z
have the fix in 4.6.z
CU is on OCP 4.6 EUS and their plan is to upgrade to next EUS which could likely be 4.10.
Thus, they look forward to get this fix backported to 4.6.
Hi Aniket, Ben
From the last information you shared, the fix is included in RHOCP 4.6.42
From the Release Notes (https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html#ocp-4-6-42),
I was able to find the Errata RHBA-2021:3008 (https://access.redhat.com/errata/RHBA-2021:3008)
and then the Bugzilla 1985347 (https://bugzilla.redhat.com/show_bug.cgi?id=1985347).
But I'm wondering why the customer has faced the issue when updating to 4.6.42!
Does the fix prevent future issues, after updating to 4.6.42?
Or should have the fix avoid the issue in 4.6.42?
In the first case, we can say that the fix has already been backported in 4.6.42 and this BZ can be closed.
In another hand, if the fix was supposed to avoid this issue in 4.6.42, something is not working as expected.
And we may need to work on this again.
Hi Aniket, Ben,
Customer updated from 4.6.42 to 4.6.45 without issues. This BZ can be closed.
Thank you for your assistance.