Skip to content

MCO-2541: Add TestRename for kubelet TLS configuration test - #824

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift-eng:mainfrom
redhat-chai-bot:kubelet-tls-test-rename
Sep 9, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift-eng:mainfrom
redhat-chai-bot:kubelet-tls-test-rename

Conversation

@machine424

@machine424 machine424 commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Map the renamed test "[sig-node][Serial] Kubelet TLS configuration should upgrade kubelet TLS from 1.2 to 1.3 on a custom pool" to its old name so Component Readiness can track it across the rename in openshift/origin PR #31547.

test renamed in openshift/origin#31547

@openshift-ci
openshift-ci Bot requested review from dgoodwin and petr-muller August 21, 2026 14:21
@machine424 machine424 changed the title Add TestRename for kubelet TLS configuration test WIP: Add TestRename for kubelet TLS configuration test Aug 21, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 21, 2026
Map the renamed test "[sig-node][Serial] Kubelet TLS configuration
should upgrade kubelet TLS from 1.2 to 1.3 on a custom pool" to its
old name so Component Readiness can track it across the rename in
openshift/origin PR #31547.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@redhat-chai-bot
redhat-chai-bot force-pushed the kubelet-tls-test-rename branch from 71d6d48 to 2614fa0 Compare August 26, 2026 07:00
@machine424

machine424 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

/retitle MCO-2541: Add TestRename for kubelet TLS configuration test

@openshift-ci openshift-ci Bot changed the title WIP: Add TestRename for kubelet TLS configuration test MCO-2541: Add TestRename for kubelet TLS configuration test Aug 26, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 26, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 26, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 26, 2026

Copy link
Copy Markdown

@machine424: This pull request references MCO-2541 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Map the renamed test "[sig-node][Serial] Kubelet TLS configuration should upgrade kubelet TLS from 1.2 to 1.3 on a custom pool" to its old name so Component Readiness can track it across the rename in openshift/origin PR #31547.

test renamed in openshift/origin#31547

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.

@neisw

neisw commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, neisw

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 Sep 9, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 78c0ee9 into openshift-eng:main Sep 9, 2026
4 checks passed
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-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants