[release-4.13] OCPBUGS-28211: add ignore for SAST scan

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1824

/assign kannon92

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-24404 has been cloned as Jira Issue OCPBUGS-28211. Will retitle bug to link to clone.
/retitle [release-4.13] OCPBUGS-28211: add ignore for SAST scan

In response to this:

This is an automated cherry-pick of #1824

/assign kannon92

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]

@openshift-cherrypick-robot: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 8b31260|UPSTREAM: : add ignore for SAST scan: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-28211, which is invalid:

• expected dependent Jira Issue OCPBUGS-24404 to target a version in 4.14.0, 4.14.z, but it targets "4.16.0" 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:

This is an automated cherry-pick of #1824

/assign kannon92

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign mfojtik for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-ci]

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	8b31260	link	true	/test unit
ci/prow/e2e-gcp-ovn-upgrade	8b31260	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/verify-commits	8b31260	link	true	/test verify-commits
ci/prow/verify	8b31260	link	true	/test verify
ci/prow/integration	8b31260	link	true	/test integration

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.

[kannon92]

/jira refresh

[openshift-ci-robot]

@kannon92: This pull request references Jira Issue OCPBUGS-28211, which is invalid:

• expected dependent Jira Issue OCPBUGS-24404 to target a version in 4.14.0, 4.14.z, but it targets "4.13" 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:

/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.

[kannon92]

/jira refresh

[openshift-ci-robot]

@kannon92: This pull request references Jira Issue OCPBUGS-28211, which is invalid:

• expected dependent Jira Issue OCPBUGS-24404 to target a version in 4.14.0, 4.14.z, but it targets "4.13" 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:

/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.

[kannon92]

/close

[openshift-ci]

@kannon92: Closed this PR.

In response to this:

/close

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-28211. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

This is an automated cherry-pick of #1824

/assign kannon92

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.