[RHACS] [Docs] [rhacs-docs-4.10] ROX-33859: Release notes for 4.10.1#109152
[RHACS] [Docs] [rhacs-docs-4.10] ROX-33859: Release notes for 4.10.1#109152agantony wants to merge 1 commit intoopenshift:rhacs-docs-4.10from
Conversation
agantony
added
ok-to-test
|
@agantony: This pull request references ROX-33859 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
size/M
|
@agantony: This pull request references ROX-33859 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@agantony: This pull request references ROX-33859 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Fri Mar 27 15:59:01 - Prow CI generated the docs preview: |
agantony
force-pushed
the
ROX33859-rhacs-docs-4.10
branch
from
664b10f to
8abdeae
Compare
|
@agantony: This pull request references ROX-33859 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
agantony
force-pushed
the
ROX33859-rhacs-docs-4.10
branch
2 times, most recently
from
48961db to
985ba66
Compare
ROX33859 Release date ROX33859 Minor fix ROX33859 Minor fix ROX33859 Minor fix
agantony
force-pushed
the
ROX33859-rhacs-docs-4.10
branch
from
985ba66 to
6c1782f
Compare
|
@agantony: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| * 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. | ||
|
|
||
| //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:
| * 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. | |
| * Before this update, selected execution paths in Sensor did not check whether the cluster entities store history was enabled or disabled. This would lead to memory being allocated and never used for clusters with enabled 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 because it no longer stores unnecessary items in the cluster entities store history. |
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.
| * 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. | ||
|
|
||
| //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.
| * 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. | |
| * Before this update, the `endpointsStore.addToHistory` function ran with quadratic computational 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. |
or maybe simpler?
| * 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. | |
| * Before this update, the `endpointsStore.addToHistory` function performed unnecessary operations, which increased sensor CPU load and elevated event-processing latency in larger clusters. 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.
Oops, I was reviewing at the same time as you were, so Agil, please disregard my comments. :)
| * 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. |
There was a problem hiding this comment.
| * 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. | |
| * 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, Red{nbsp}Hat corrected the issue with inaccurate data processing in the report generator. As a result, the system no longer hangs during data transfer. |
| * 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. | ||
|
|
||
| //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. |
There was a problem hiding this comment.
| * 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. | |
| * 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. |
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.
| * 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. | ||
|
|
||
| //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. |
There was a problem hiding this comment.
| * 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. | |
| * Before this update, merging many alerts triggered heavy queries for unnecessary full alerts, which caused performance issues during non-merge cases. With this release, Red{nbsp}Hat has improved performance by fetching only the necessary fields in `mergeManyAlerts`. As a result, merging alerts occurs faster, improving overall system efficiency for users. |
IBM SG recommends against "we": https://www.ibm.com/docs/en/ibm-style?topic=word-usage#word-usage__w__title__1
| * 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. | ||
|
|
||
| //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. |
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.
| * 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. | ||
|
|
||
| //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.
| * 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. | |
| * Before this update, the system did not check whether the cluster entities store history enabled or disabled history. With this release, Red{nbsp}Hat 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. |
Something is off with this sentence: "whether the cluster entities store history enabled or disabled history" - it doesn't make sense to me
| * 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. | ||
|
|
||
| //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.
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?
There was a problem hiding this comment.
Never mind, I see that Piotr reviewed as I was adding these comments.
| 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. |
There was a problem hiding this comment.
| * 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. | |
| * 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. |
kcarmichael08
added
the
peer-review-done
5 participants
Version(s):
4.10
Issue:
https://redhat.atlassian.net/browse/ROX-33859
Link to docs preview:
SME review:
Additional information:
No cherrypicking