-
Bug
-
Resolution: Obsolete
-
Normal
-
None
-
4.13, 4.12, 4.11, 4.10, 4.14
-
Moderate
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
OCPBUGS-12002 and its backports are not listed in the release notes (errata) for their fixes. I understand that this is due to the JIRA tickets being private, which makes the links inaccessible to external users, and therefore, listing them in the publicly accessible Errata would be ineffective as they cannot be viewed. However, this situation leaves users without a way to learn about the fixes. OCPBUGS-12002 is a bug that affects many user environments and should be publicly disclosed. Can we consider listing it in the errata without the ticket link, or find some alternative method? This ticket is based on the request that users want to regularly check for significant bugs to plan appropriate upgrades. This is a very exemplary operational style, and as a product, we should support such actions.
Actual results:
Unable to obtain fix information from the release notes. Specifically, the issue is as follows:
For version 4.14.0: JIRA Ticket: OCPBUGS-12002 Errata: RHSA-2023:5006
For version 4.13.5: JIRA Ticket: OCPBUGS-13745 Errata: RHSA-2023:4091
For version 4.12.27: JIRA Ticket: OCPBUGS-15593 Errata: RHBA-2023:4319
For version 4.11.47: JIRA Ticket: OCPBUGS-16691 Errata: RHBA-2023:4614
For version 4.10.66: JIRA Ticket: OCPBUGS-17165 Errata: RHBA-2023:4667
Expected results:
List the bug and its fix information in the above-mentioned release notes.
Additional info:
The KCS article related to this issue is as follows. It mentions the fixed version, but users are unable to verify whether the fix has actually been implemented. https://access.redhat.com/solutions/6646561
I understand that making JIRA tickets private to avoid security incidents of information leakage, as they contain customer information like logs and "must-gather" for investigation purposes. However, in such cases, instead of omitting the fix information entirely from the release notes, couldn’t we describe the bug and its fix using methods other than JIRA tickets?
