OCPBUGS-26162: Fixed .snyk format

[rbaturov]

Previous format was wrong, and in turn had no effect on ignoring code issues.

[openshift-ci-robot]

@rbaturov: This pull request references Jira Issue OCPBUGS-26162, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Previous format was wrong, and in turn had no effect on ignoring code issues.

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]

@rbaturov: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Previous format was wrong, and in turn had no effect on ignoring code issues.

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.

[ffromani]

/lgtm

snyk docs are surprising at times

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, rbaturov

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ffromani]

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

[openshift-ci-robot]

@rbaturov: This pull request references Jira Issue OCPBUGS-26162, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Previous format was wrong, and in turn had no effect on ignoring code issues.

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.

[rbaturov]

/retest-required

[rbaturov]

/retest-required

[yanirq]

/label acknowledge-critical-fixes-only label

[rbaturov]

/jira refresh

[openshift-ci-robot]

@rbaturov: This pull request references Jira Issue OCPBUGS-26162, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (liqcui@redhat.com), skipping review request.

In response to this:

/jira refresh

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]

/retest-required

Remaining retests: 0 against base HEAD 1356994 and 2 for PR HEAD a4c3304 in total

[openshift-ci]

@rbaturov: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@rbaturov: Jira Issue OCPBUGS-26162: All pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#902
• openshift/cluster-node-tuning-operator#1000

Jira Issue OCPBUGS-26162 has been moved to the MODIFIED state.

In response to this:

Previous format was wrong, and in turn had no effect on ignoring code issues.

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202403251813.p0.gc599930.assembly.stream.el9 for distgit cluster-node-tuning-operator.
All builds following this will include this PR.