OCPBUGS-28230: enforce termination message policy on all platform pods

[deads2k]

found in https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-techpreview-serial/1785629293024382976

We want to be sure we are getting logs from failed containers.

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-28230, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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:

found in https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-techpreview-serial/1785629293024382976

We want to be sure we are getting logs from failed containers.

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.

[deads2k]

/jira refresh

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-28230, 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)

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.

[JoelSpeed]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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

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

[openshift-ci]

@deads2k: The following test 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/e2e-azure-ovn-techpreview	f25e9a8	link	false	/test e2e-azure-ovn-techpreview

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]

@deads2k: Jira Issue OCPBUGS-28230: Some pull requests linked via external trackers have merged:

• openshift/cloud-credential-operator#663
• openshift/machine-api-operator#1211
• openshift/origin#28547
• openshift/machine-config-operator#4147
• openshift/cluster-network-operator#2224
• openshift/cluster-ingress-operator#1019
• openshift/cluster-machine-approver#227
• openshift/cluster-samples-operator#532
• openshift/cluster-image-registry-operator#992
• openshift/cluster-autoscaler-operator#312
• openshift/service-ca-operator#230
• openshift/cluster-baremetal-operator#399
• openshift/oc#1667
• openshift/cluster-dns-operator#403
• openshift/cluster-cloud-controller-manager-operator#330
• openshift/cloud-credential-operator#672
• openshift/cluster-control-plane-machine-set-operator#274
• openshift/cluster-csi-snapshot-controller-operator#193
• openshift/aws-efs-csi-driver-operator#126
• openshift/aws-load-balancer-operator#131
• openshift/external-dns-operator#215
• openshift/machine-config-operator#4318
• openshift/csi-operator#214
• openshift/operator-framework-olm#733
• openshift/machine-config-operator#4319
• openshift/cluster-network-operator#2334
• openshift/release#50875
• openshift/cluster-network-operator#2340
• openshift/cluster-baremetal-operator#413
• openshift/csi-operator#216
• operator-framework/operator-marketplace#559
• openshift/origin#28721
• openshift/vmware-vsphere-csi-driver-operator#229
• openshift/openstack-cinder-csi-driver-operator#166
• openshift/csi-driver-manila-operator#229
• openshift/gcp-filestore-csi-driver-operator#91
• openshift/gcp-pd-csi-driver-operator#119
• openshift/secrets-store-csi-driver-operator#49
• openshift/csi-driver-shared-resource-operator#107
• openshift/local-storage-operator#477
• openshift/origin#28728
• openshift/cluster-network-operator#2354
• openshift/cluster-storage-operator#467
• openshift/ibm-powervs-block-csi-driver-operator#70

The following pull requests linked via external trackers have not merged:

• openshift/operator-framework-catalogd#49 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

found in https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-techpreview-serial/1785629293024382976

We want to be sure we are getting logs from failed containers.

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 ose-cluster-capi-operator-container-v4.16.0-202405012344.p0.gccded70.assembly.stream.el9 for distgit ose-cluster-capi-operator.
All builds following this will include this PR.