[RHACS] [Docs] [rhacs-docs-4.10] ROX-33859: Release notes for 4.10.1 #109152
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,37 @@ | ||||||||||
| // Module included in the following assemblies: | ||||||||||
| // | ||||||||||
| // * release_notes/410-release-notes.adoc | ||||||||||
|
|
||||||||||
| :_mod-docs-content-type: REFERENCE | ||||||||||
| [id="bug-fixes_4101"] | ||||||||||
| = Bug fixes in version 4.10.1 | ||||||||||
|
|
||||||||||
| [role="_abstract"] | ||||||||||
| This release has bug fixes and patches addressing a security vulnerability. | ||||||||||
|
|
||||||||||
| This release provides the following bug fixes: | ||||||||||
|
|
||||||||||
| //ROX-33295 | ||||||||||
| * Before this update, images with empty names were improperly uploaded, causing global search to return blank image results. With this release, empty-named images no longer appear in search results, enhancing search efficiency. | ||||||||||
|
|
||||||||||
| //ROX-33325 | ||||||||||
| * Before this update, the script failed to run on a Linux system due to missing executable program permissions, causing user interface elements to display incorrectly. With this release, the bug fix corrected the issue with inaccurate data processing in the report generator. As a result, the system no longer hangs during data transfer, enhancing user productivity. | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
|
|
||||||||||
| //ROX-33548 | ||||||||||
| * Before this update, missing executable permissions prevented the script from running on Linux, which caused user interface elements to display incorrectly. With this release, the update corrects the inaccurate data processing in the report generator. As a result, the system transfers data without hanging, which boosts user productivity. | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
I'm going to keep removing these statements about productivity. If they are bug fixes, obviously they are going to increase productivity if the system works properly. IMO this is one of the worst parts of AI - stating something obvious just to make up "benefits" to create words. |
||||||||||
|
|
||||||||||
| //ROX-33626 | ||||||||||
| * Before this update, merging many alerts triggered heavy queries for unnecessary full alerts, which caused performance issues during non-merge cases. With this release, we have improved performance by fetching only the necessary fields in `mergeManyAlerts`. As a result, merging alerts occurs faster, improving overall system efficiency for users. | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
IBM SG recommends against "we": https://www.ibm.com/docs/en/ibm-style?topic=word-usage#word-usage__w__title__1 |
||||||||||
|
|
||||||||||
| //ROX-33686 | ||||||||||
| * Before this update, {ocp} 4.22 dropped `PatternFly` 5 support, causing runtime issues with the plugin in {ocp} 4.21 and later. As a consequence, users encountered runtime issues due to the disabled plugin. With this release, Red{nbsp}Hat updated the {ocp} version list for the dynamic plugin in versions 4.19, 4.20, and 4.21, disabling `PatternFly` 5 in {ocp} 4.21 and later. As a result, this avoids runtime issues, improving overall stability. | ||||||||||
|
Contributor
There was a problem hiding this comment. This isn't a bug fix. This is actually a "known issue" that the plugin does not work with OCP 4.22, so it is disabled. This needs to not be stated as a bug fix, but as a "known issue" and reframed as, due to PatternFly 5 not being supported, the plugin is disabled for OCP version 4.22. In addition I don't think it's accurate to say that we disabled PatternFly support in 4.21 and later. OCP did, and that's not part of anything we did. We disabled the plugin because of that action. @dvail can you help with wording? Suggest we create a separate module for known issues and list there. |
||||||||||
|
|
||||||||||
| //ROX-33757 | ||||||||||
| * Before this update, the system did not check whether the cluster entities store history enabled or disabled history. With this release, we have added a check for cluster entities history to prevent unnecessary storage. As a result, the system maintains optimal memory usage and CPU load because it no longer stores unnecessary items in the cluster entities store history. | ||||||||||
|
There was a problem hiding this comment. I think, this statement is too strong. The missing check for the history being enabled was affecting only an edge-case scenario and the unnecessary memory consumption was limited to couple of MBs. The impact of that was small as we could not detect the lost memory from memory profiles (it should be visible there), but only by looking at the code. Let me give it a shot:
Suggested change
I added a sentence about the consequences for the affected systems (memory allocated and never used) and specified that the issue was affecting only those Sensors where history was enabled.
Contributor
There was a problem hiding this comment.
Suggested change
Something is off with this sentence: "whether the cluster entities store history enabled or disabled history" - it doesn't make sense to me |
||||||||||
|
|
||||||||||
| //ROX-33758 | ||||||||||
| * Before this update, the `endpointsStore.addToHistory` function caused quadratic complexity in large clusters, which increased sensor CPU load and elevated event-processing latency. With this release, we have improved CPU efficiency in `endpointsStore` mutations to reduce latency. As a result, the system processes events faster and maintains lower CPU usage in large clusters with many endpoints. | ||||||||||
|
There was a problem hiding this comment.
Suggested change
or maybe simpler?
Suggested change
Contributor
There was a problem hiding this comment. Oops, I was reviewing at the same time as you were, so Agil, please disregard my comments. :)
Contributor
There was a problem hiding this comment. This is the kind of fix that I don't think needs to be in the Release Notes. It is more of an internal optimization and all customers really care about is that the system works better. If we do want to "advertise" it, I think it should be simplified as "Fixed an issue which resulted in improved CPU efficiency." or something similar. @vikin91 , WDYT?
Contributor
There was a problem hiding this comment. Never mind, I see that Piotr reviewed as I was adding these comments. |
||||||||||
|
|
||||||||||
| This release also addresses the following security vulnerability: | ||||||||||
|
|
||||||||||
| * Incorrect IPv6 host literal parsing in net/url allows for improper URL validation and handling (link:https://access.redhat.com/security/cve/cve-2026-25679[CVE-2026-25679]) | ||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.