ignore ErrNotDynLinked for all valgrind rpm files

[jctanner]

We've encountered ErrNotDynLinked errors on valgrind with multiple RHOAI images. Given valgrind is not performing cryptographic operations, is not a golang binary and would generally not compile any differently with CGO_ENABLED=1, we'd like to make a blanket ignore on it's files.

---- Failure Report
+----------------+---------------------------+----------------------------------------------+--------------------------------------+------------------------------------+
| OPERATOR NAME  | RPM NAME                  | EXECUTABLE NAME                              | STATUS                               | IMAGE                              |
+----------------+---------------------------+----------------------------------------------+--------------------------------------+------------------------------------+
| ubi9-container | habanalabs-firmware-tools | /usr/bin/hl-smi                              | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/cachegrind-amd64-linux | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/callgrind-amd64-linux  | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/dhat-amd64-linux       | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/drd-amd64-linux        | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/exp-bbv-amd64-linux    | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/helgrind-amd64-linux   | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/lackey-amd64-linux     | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/massif-amd64-linux     | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/memcheck-amd64-linux   | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
| ubi9-container | valgrind                  | /usr/libexec/valgrind/none-amd64-linux       | executable is not dynamically linked | quay.io/modh/vllm:rhoai-2.19-gaudi |
+----------------+---------------------------+----------------------------------------------+--------------------------------------+------------------------------------+

[openshift-ci]

@jctanner: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

[rphillips]

/lgtm

[rhmdnd]

I think this will exclude for all OCP versions. Is that what we want or can we make this more specific to the release it's affecting by contributing it to https://github.com/openshift/check-payload/tree/main/dist/releases/4.20 for example?

[jctanner]

We're encountering these failures in component images for Red Hat Openshift AI, which supports multiple OCP versions. Currently 4.14 to 4.18 per https://access.redhat.com/support/policy/updates/rhoai-sm/lifecycle ... so unfortunately can't pin this exception to specific OCP version.

[rhmdnd]

We should be able to add the exclusion to each affected OCP version in dist/releases then.

[rhmdnd]

But since this is going to be rolled forward for all new versions of OpenShift, then we can probably DRY things up by keeping this in the global config.

Thanks for walking me through this.

[rhmdnd]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jctanner, rhmdnd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rhmdnd]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment