OCPBUGS-42547: [release-1.31] : config: fix validation of allowed annotations

[openshift-cherrypick-robot]

This is an automated cherry-pick of #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

[openshift-ci-robot]

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-42547 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

/retitle [release-1.31] : config: fix validation of allowed annotations

In response to this:

This is an automated cherry-pick of #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

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-ci-robot: This pull request references Jira Issue OCPBUGS-42547, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-42547 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-42547 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

/retitle [release-1.31] : config: fix validation of allowed annotations

In response to this:

This is an automated cherry-pick of #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

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.

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: 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:

This is an automated cherry-pick of #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

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.

[haircommander]

/lgtm
/approve

[openshift-ci-robot]

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

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-42547 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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 #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

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.

[kwilczynski]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, kwilczynski, openshift-cherrypick-robot

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

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 46.75%. Comparing base (9704b0c) to head (f334f80).
Report is 2 commits behind head on release-1.31.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-1.31    #8710      +/-   ##
================================================
+ Coverage         46.73%   46.75%   +0.01%     
================================================
  Files               153      153              
  Lines             22035    22035              
================================================
+ Hits              10298    10302       +4     
+ Misses            10669    10666       -3     
+ Partials           1068     1067       -1     

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-42547: All pull requests linked via external trackers have merged:

• cri-o/cri-o#8710

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

In response to this:

This is an automated cherry-pick of #8628

/assign haircommander

fix a bug where an `allowed_annotation` specified twice (in either a workload or runtime) couldn't be used

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.

[haircommander]

/cherry-pick release-1.30

[openshift-cherrypick-robot]

@haircommander: new pull request created: #8712

In response to this:

/cherry-pick release-1.30

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.