Skip to content

[release-4.22] OCPBUGS-86118: Add unit and e2e test coverage for cert rotation redeployment#1161

Open
jhadvig wants to merge 1 commit into
openshift:release-4.22from
jhadvig:OCPBUGS-86118
Open

[release-4.22] OCPBUGS-86118: Add unit and e2e test coverage for cert rotation redeployment#1161
jhadvig wants to merge 1 commit into
openshift:release-4.22from
jhadvig:OCPBUGS-86118

Conversation

@jhadvig
Copy link
Copy Markdown
Member

@jhadvig jhadvig commented May 19, 2026

Summary

  • Cherry-pick of 0a408ad adding unit and e2e test coverage for cert rotation redeployment
  • Follow-up to OCPBUGS-63502 fix which was merged without test coverage
  • Adds TestServingCertAnnotationChangesOnRotation, TestServingCertAnnotationInResourceAnnotations (unit) and TestCertRotationTriggersRollout (e2e)

Test plan

  • Unit tests pass: go test ./pkg/console/subresource/deployment/ -run TestServingCert
  • E2E test passes on a cluster: TestCertRotationTriggersRollout

Jira: https://issues.redhat.com/browse/OCPBUGS-86118

@openshift-ci-robot openshift-ci-robot added 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 May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jhadvig: This pull request references Jira Issue OCPBUGS-86118, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set
  • 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 dependent Jira Issue OCPBUGS-86117 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
  • expected dependent Jira Issue OCPBUGS-86117 to target a version in 5.0.0, but no target version was set

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:

Summary

  • Cherry-pick of 0a408ad adding unit and e2e test coverage for cert rotation redeployment
  • Follow-up to OCPBUGS-63502 fix which was merged without test coverage
  • Adds TestServingCertAnnotationChangesOnRotation, TestServingCertAnnotationInResourceAnnotations (unit) and TestCertRotationTriggersRollout (e2e)

Test plan

  • Unit tests pass: go test ./pkg/console/subresource/deployment/ -run TestServingCert
  • E2E test passes on a cluster: TestCertRotationTriggersRollout

Jira: https://issues.redhat.com/browse/OCPBUGS-86118

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
Copy link
Copy Markdown

coderabbitai Bot commented May 19, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 28d758e3-ee48-4b53-b236-5db4b59e029e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

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

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

@openshift-ci openshift-ci Bot requested review from TheRealJon and spadgett May 19, 2026 11:11
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2026
@jhadvig jhadvig changed the title OCPBUGS-86118: Add unit and e2e test coverage for cert rotation redeployment [release-4.22] OCPBUGS-86118: Add unit and e2e test coverage for cert rotation redeployment May 19, 2026
@jhadvig jhadvig 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 May 19, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

@jhadvig: 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-aws-console 4cf73e5 link true /test e2e-aws-console

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/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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants