[DNM] Openshift paco fix

[harche]

Testing Openshift CI for this upstream PR https://github.com/kubernetes/kubernetes/pull/122763/commits

[openshift-ci-robot]

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

• 236b9ae|add log for whether trigger start/restart for Created state: does not specify an upstream backport in the commit message
• 52b4c1e|for CREATED state, skip if EventedPLEG is enabled: does not specify an upstream backport in the commit message
• ce0c933|delete channel from the terminated after closing it: does not specify an upstream backport in the commit message
• dd643fe|fix eventedPLEG flake: init container may waiting with empty reason before seeting it to PodInitializing: 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: harche
Once this PR has been reviewed and has the lgtm label, please assign tkashem 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

[rphillips]

/payload 4.16 ci blocking
/payload 4.16 nightly blocking

[openshift-ci]

@rphillips: trigger 5 job(s) of type blocking for the ci release of OCP 4.16

• periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-azure-sdn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-e2e-aws-sdn-serial
• periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/756c5560-b3c4-11ee-96b2-22bf8965744e-0

trigger 8 job(s) of type blocking for the nightly release of OCP 4.16

• periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-sdn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-sdn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/756c5560-b3c4-11ee-96b2-22bf8965744e-1

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale