Skip to content

OCPBUGS-84512: Remove exception terminationMessagePolicy=TerminationMessageFallbackToLogsOnError#31327

Open
theobarberbany wants to merge 1 commit into
openshift:mainfrom
theobarberbany:tb/remove-cloud-provider-aws-exception
Open

OCPBUGS-84512: Remove exception terminationMessagePolicy=TerminationMessageFallbackToLogsOnError#31327
theobarberbany wants to merge 1 commit into
openshift:mainfrom
theobarberbany:tb/remove-cloud-provider-aws-exception

Conversation

@theobarberbany

@theobarberbany theobarberbany commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Removes the exception for cloud-provider-aws on terminationMessagePolicy=FallbackToLogsOnError violations

Fixed by openshift/release#80840

Summary by CodeRabbit

  • Bug Fixes
    • Stricter validation enforcement: Removed grandfathered exceptions for a namespace, ensuring TerminationMessagePolicy violations are now properly reported and cannot bypass validation checks.

…essageFallbackToLogsOnError

Removes the exception for cloud-provider-aws on terminationMessagePolicy=FallbackToLogsOnError violations
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot

Copy link
Copy Markdown

@theobarberbany: No Jira issue with key CPBUGS-84512 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Removes the exception for cloud-provider-aws on terminationMessagePolicy=FallbackToLogsOnError violations

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.

@theobarberbany theobarberbany changed the title CPBUGS-84512: Remove exception terminationMessagePolicy=TerminationMessageFallbackToLogsOnError OCPBUGS-84512: Remove exception terminationMessagePolicy=TerminationMessageFallbackToLogsOnError Jun 23, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 23, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@theobarberbany: This pull request references Jira Issue OCPBUGS-84512, which is invalid:

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

Details

In response to this:

Removes the exception for cloud-provider-aws on terminationMessagePolicy=FallbackToLogsOnError violations

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.

@theobarberbany

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@theobarberbany: This pull request references Jira Issue OCPBUGS-84512, which is invalid:

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

Details

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.

@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Walkthrough

The openshift-cloud-controller-manager namespace entry is removed from the existingViolations grandfathered exceptions map in the termination message policy monitor test, meaning pods in that namespace are no longer exempt from TerminationMessagePolicy violation reporting. A minor block layout adjustment is also made to the ephemeralContainers loop.

Changes

Remove CCM namespace from termination message policy exemptions

Layer / File(s) Summary
Remove CCM exemption and loop formatting
pkg/monitortests/clusterversionoperator/terminationmessagepolicy/monitortest.go
Deletes the openshift-cloud-controller-manager entry from existingViolations, removing its grandfathered exemption from TerminationMessagePolicy checks. Adjusts ephemeralContainers loop block spacing with no logic change.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: removing an exception for terminationMessagePolicy violations in the openshift-cloud-controller-manager namespace, which aligns with the code changes shown in the diff.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR only removes entries from existingViolations map and makes no changes to test name generation code. The existing test names use static Kubernetes namespace names (e.g., openshift-cluster-version...
Test Structure And Quality ✅ Passed The PR modifies monitortest.go (monitor test implementation) and monitortest_test.go (Go unit test using testing package). Neither contains Ginkgo tests, so the Ginkgo test quality check is not app...
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e tests are added in this PR. The changes only modify validation logic in an existing monitor test (not an e2e test), specifically removing an exception entry from the existingViola...
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR modifies a monitor test framework file, not a Ginkgo e2e test. The custom check only applies to new Ginkgo e2e tests (It(), Describe(), etc.), which are not present in this PR.
Topology-Aware Scheduling Compatibility ✅ Passed PR only removes an exception from a monitor test file; no deployment manifests, operator code, or scheduling constraints are introduced or modified.
Ote Binary Stdout Contract ✅ Passed PR removes 3 lines (2 blank lines and 1 map entry) with no fmt.Print*, log.Print, or klog stdout writes in init() or process-level code. OTE stdout contract satisfied.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds no Ginkgo e2e tests; it modifies a monitoring test framework component that implements monitortestframework.MonitorTest, not Ginkgo test patterns.
No-Weak-Crypto ✅ Passed The PR modifies only a monitoring/testing file for Kubernetes pod configuration validation. It contains no cryptographic code, weak crypto algorithms, or related security patterns.
Container-Privileges ✅ Passed PR modifies a monitoring test file to remove an exception from a grandfathered violations map. No container privilege configurations (privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPriv...
No-Sensitive-Data-In-Logs ✅ Passed No sensitive data (passwords, tokens, API keys, PII, etc.) is logged. PR only removes an exception entry and formatting; no new logging statements introducing sensitive data.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@theobarberbany

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 23, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@theobarberbany: This pull request references Jira Issue OCPBUGS-84512, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

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.

@openshift-ci openshift-ci Bot requested review from deads2k and sjenning June 23, 2026 11:14
@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Jun 23, 2026
@miyadav

miyadav commented Jun 23, 2026

Copy link
Copy Markdown
Member

/approve

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 23, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@theobarberbany

Copy link
Copy Markdown
Contributor Author

/pipeline auto

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

The /pipeline auto command is only available for LGTM-mode repositories. For repositories in automatic mode, second-stage tests are already triggered automatically.

@miyadav

miyadav commented Jun 23, 2026

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 23, 2026
@openshift-ci

openshift-ci Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: miyadav, theobarberbany

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@miyadav

miyadav commented Jun 23, 2026

Copy link
Copy Markdown
Member

/test e2e-gcp-ovn

@theobarberbany

Copy link
Copy Markdown
Contributor Author

@miyadav The GCP failures are unrelated to this change, can we override?

@miyadav

miyadav commented Jun 24, 2026

Copy link
Copy Markdown
Member

/override e2e-gcp-ovn

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@miyadav: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • e2e-gcp-ovn

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • ci/prow/e2e-aws-csi
  • ci/prow/e2e-aws-ovn-fips
  • ci/prow/e2e-aws-ovn-microshift
  • ci/prow/e2e-aws-ovn-microshift-serial
  • ci/prow/e2e-aws-ovn-serial-1of2
  • ci/prow/e2e-aws-ovn-serial-2of2
  • ci/prow/e2e-gcp-csi
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-gcp-ovn-upgrade
  • ci/prow/e2e-metal-ipi-ovn-ipv6
  • ci/prow/e2e-vsphere-ovn
  • ci/prow/e2e-vsphere-ovn-upi
  • ci/prow/go-verify-deps
  • ci/prow/images
  • ci/prow/lint
  • ci/prow/okd-scos-images
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-origin-main-e2e-aws-csi
  • pull-ci-openshift-origin-main-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-main-e2e-aws-ovn-microshift
  • pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial
  • pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2
  • pull-ci-openshift-origin-main-e2e-aws-ovn-serial-2of2
  • pull-ci-openshift-origin-main-e2e-gcp-csi
  • pull-ci-openshift-origin-main-e2e-gcp-ovn
  • pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
  • pull-ci-openshift-origin-main-go-verify-deps
  • pull-ci-openshift-origin-main-images
  • pull-ci-openshift-origin-main-lint
  • pull-ci-openshift-origin-main-okd-scos-images
  • pull-ci-openshift-origin-main-unit
  • pull-ci-openshift-origin-main-verify
  • pull-ci-openshift-origin-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override e2e-gcp-ovn

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.

@miyadav

miyadav commented Jun 24, 2026

Copy link
Copy Markdown
Member

/override ci/prow/e2e-gcp-ovn

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@miyadav: Overrode contexts on behalf of miyadav: ci/prow/e2e-gcp-ovn

Details

In response to this:

/override ci/prow/e2e-gcp-ovn

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

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@theobarberbany: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants