[openshift-4.19] Do not trigger rebuilds for pinned rpm

[openshift-cherrypick-robot]

This is an automated cherry-pick of #6680

/assign mbiarnes

[mbiarnes]

/lgtm
/approve
/cherrypick openshift-4.18

[openshift-cherrypick-robot]

@mbiarnes: once the present PR merges, I will cherry-pick it on top of openshift-4.18 in a new PR and assign it to you.

In response to this:

/lgtm
/approve
/cherrypick openshift-4.18

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mbiarnes

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 [mbiarnes]

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

[openshift-cherrypick-robot]

@mbiarnes: #6681 failed to apply on top of branch "openshift-4.18":

Applying: Do not trigger rebuilds for pinned rpm
Using index info to reconstruct a base tree...
M	images/ose-frr.yml
Falling back to patching base and 3-way merge...
Auto-merging images/ose-frr.yml
CONFLICT (content): Merge conflict in images/ose-frr.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Do not trigger rebuilds for pinned rpm

In response to this:

/lgtm
/approve
/cherrypick openshift-4.18

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.