Skip to content

[rhacs-docs-4.1] ROX-17004: Updating BPF CO-RE section and adding known issue #61881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kcarmichael08 merged 1 commit into from
Jun 28, 2023
Merged

[rhacs-docs-4.1] ROX-17004: Updating BPF CO-RE section and adding known issue #61881

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions release_notes/41-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ toc::[]
[options="header"]
|====
|{product-title-short} version |Released on
|`4.1` |26 Jun 2023
|`4.1` |29 Jun 2023
|====

[id="about-this-release_{context}"]
Expand Down Expand Up @@ -125,7 +125,7 @@ With this release, you can test a new runtime collection method that no longer r
:FeatureName: The `CORE_BPF` collection method
include::snippets/technology-preview.adoc[leveloffset=+1]

This feature is available for testing on the x86_64 architecture and is based on the new Linux BPF features, including CO-RE (Compile Once-Run Everywhere). To enable it, set the value of the `collector.collectionMethod` parameter of your backed-up cluster to `CORE_BPF`.
This feature is available for testing on `x86_64` and `s390x` architectures and is based on the new Linux BPF features, including CO-RE (Compile Once-Run Everywhere). To enable it, set the value of the `collector.collectionMethod` parameter of your backed-up cluster to `CORE_BPF`.

The new method offers several advantages:

Expand Down Expand Up @@ -393,6 +393,7 @@ When Central was reinstalled, the password of the new secret didn't match the on
[id="known-issues_{context}"]
=== Known issues

* For secured clusters on {ibm-z} and {ibm-linuxone} that are running {ocp} 4.10, Collector fails to start when the default configuration is used. As a workaround, enable the xref:../release_notes/41-release-notes.adoc#new-collection-method-based-on-bpf-co-re-technology-preview_release-notes-41[CORE_BPF collection method] (Technology Preview). (ROX-18058)
* For secured clusters on {ibm-z} and {ibm-linuxone}, there is a known issue with the Process Group Identifier (GID) in the `ProcessesService` API where the reported GID can be incorrect and display a value of `-1`. This affects process details provided through the `/v1/processes/deployment/{deploymentId}` API endpoint and other APIs that provide process signal information.
+
This can lead to inaccuracies or inconsistencies in the reported GID. This issue does not impact the {product-title-short} portal or policy criteria. Also, when using ePBF on {ibm-z} and {ibm-linuxone}, the GID process might be invalid (`-1`) for processes that terminate shortly after execution. There is currently no workaround for this issue. (ROX-17459)
Expand Down