Skip to content

Revert "OCPCLOUD-3347: tls: use centralized TLS profile" - #291

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
neisw:revert-286-use-centralized-tls-profile
Feb 25, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
neisw:revert-286-use-centralized-tls-profile

Conversation

@neisw

@neisw neisw commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

Reverts #286

Context on the revert: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1772037374218609

--

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

Payload failures due to hypershift jobs

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn

CC: @damdo

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 25, 2026
@openshift-ci-robot

openshift-ci-robot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: This pull request references OCPCLOUD-3347 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #286

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

Payload failures due to hypershift jobs

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn

CC: @damdo

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 Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn

@openshift-ci

openshift-ci Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f6ac9e90-1269-11f1-8afc-81e7fca40947-0

@neisw

neisw commented Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

/test ?

@openshift-ci

openshift-ci Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: The following commands are available to trigger required jobs:

/test e2e-aws
/test e2e-aws-capi-techpreview
/test e2e-aws-operator
/test e2e-upgrade
/test images
/test okd-scos-images
/test unit
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-azure-operator
/test e2e-gcp-operator
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cluster-machine-approver-main-e2e-aws
pull-ci-openshift-cluster-machine-approver-main-e2e-aws-capi-techpreview
pull-ci-openshift-cluster-machine-approver-main-e2e-aws-operator
pull-ci-openshift-cluster-machine-approver-main-e2e-upgrade
pull-ci-openshift-cluster-machine-approver-main-images
pull-ci-openshift-cluster-machine-approver-main-okd-scos-images
pull-ci-openshift-cluster-machine-approver-main-unit
pull-ci-openshift-cluster-machine-approver-main-verify-deps
Details

In response to this:

/test ?

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.

@bryan-cox

Copy link
Copy Markdown
Member

/lgtm

@damdo damdo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@damdo

damdo commented Feb 25, 2026

Copy link
Copy Markdown
Member

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 25, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@damdo: The verified label has been added.

Details

In response to this:

/verified bypass

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 added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@openshift-ci

openshift-ci Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo

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 Feb 25, 2026
@openshift-ci-robot

openshift-ci-robot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: This pull request references OCPCLOUD-3347 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Reverts #286

Context on the revert: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1772037374218609

--

Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.

Payload failures due to hypershift jobs

To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of these jobs to confirm the fix has corrected the problem:

/payload-job periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn

CC: @damdo

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 Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws
/override ci/prow/e2e-aws-capi-techpreview

@openshift-ci

openshift-ci Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws, ci/prow/e2e-aws-capi-techpreview

Details

In response to this:

/override ci/prow/e2e-aws
/override ci/prow/e2e-aws-capi-techpreview

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.

@neisw

neisw commented Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-upgrade

@openshift-ci

openshift-ci Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-operator, ci/prow/e2e-upgrade

Details

In response to this:

/override ci/prow/e2e-aws-operator
/override ci/prow/e2e-upgrade

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-merge-bot
openshift-merge-bot Bot merged commit 8b92e37 into openshift:main Feb 25, 2026
9 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants