Skip to content

Conversation

@jacobsee
Copy link
Member

@jacobsee jacobsee commented Mar 19, 2025

This PR:

  • Removes a skip on an existing TLS test - it appears to have been a setup issue
  • Adds a test for ensuring that components are properly listening for only the expected TLS version or higher.

cc: @dusk125

@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 Mar 19, 2025
@openshift-ci openshift-ci bot requested review from Elbehery and deads2k March 19, 2025 23:54
@jacobsee jacobsee changed the title [WIP] TLS 1.3 / Modern profile tests TLS 1.3 / Modern profile tests Mar 20, 2025
@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 Mar 20, 2025
@jacobsee
Copy link
Member Author

jacobsee commented Mar 20, 2025

Supports OCPBUGS-37706, OCPSTRAT-1364

@openshift-trt
Copy link

openshift-trt bot commented Mar 20, 2025

Job Failure Risk Analysis for sha: 6c00d75

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling High
[sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times
This test has passed 100.00% of 1 runs on jobs [periodic-ci-openshift-release-master-nightly-4.19-e2e-gcp-ovn-etcd-scaling periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-etcd-scaling] in the last 14 days.

@dusk125
Copy link
Contributor

dusk125 commented Mar 20, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2025
@jacobsee
Copy link
Member Author

/retest-required

@openshift-trt
Copy link

openshift-trt bot commented Mar 21, 2025

Job Failure Risk Analysis for sha: ff62120

Job Name Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback MissingData
pull-ci-openshift-origin-main-e2e-aws-disruptive Medium
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling Low
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
---
[bz-kube-storage-version-migrator] clusteroperator/kube-storage-version-migrator should not change condition/Available
This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
---
[bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available
This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive Medium
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis
---
[sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator
Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling Medium
[bz-etcd][invariant] alert/etcdMembersDown should not be at or above info
Potential external regression detected for High Risk Test analysis
---
[sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times
Potential external regression detected for High Risk Test analysis

@p0lyn0mial
Copy link
Contributor

which jobs run the new test ? i have checked metal-ipi-serial, aws-ovn-microshift-serial and aws-ovn-serial but didn't find the new test on the list.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 21, 2025
@openshift-trt
Copy link

openshift-trt bot commented Mar 22, 2025

Job Failure Risk Analysis for sha: b6d72fd

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-disruptive Medium
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis

@p0lyn0mial
Copy link
Contributor

which jobs run the new test ? i have checked metal-ipi-serial, aws-ovn-microshift-serial and aws-ovn-serial but didn't find the new test on the list.

@jacobsee I think you need to run make update to actually "add" the test to the list of tests to be executed. For example: https://github.com/openshift/origin/pull/29191/commits

@jacobsee
Copy link
Member Author

@p0lyn0mial Thanks! I hadn't seen that. It's in there now, and I've realized that it should probably be marked [slow] as well. To your earlier comment, do we now still need to pick jobs to run this? This is my first brush with the origin tests, so I'm not sure what all is needed to get a new one plugged in correctly.

@openshift-trt
Copy link

openshift-trt bot commented Mar 25, 2025

Job Failure Risk Analysis for sha: 39e5f22

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling Low
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 50.00% of 2 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:aws SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive High
[bz-Monitoring] clusteroperator/monitoring should not change condition/Degraded
This test has passed 99.30% of 5292 runs on release 4.19 [Overall] in the last week.
---
[bz-Monitoring] clusteroperator/monitoring should not change condition/Available
This test has passed 99.45% of 5292 runs on release 4.19 [Overall] in the last week.

@p0lyn0mial
Copy link
Contributor

To your earlier comment, do we now still need to pick jobs to run this?

it looks like you could use /payload-job-with-prs to test your new test with the o/k PR, for example:

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn openshift/kubernetes#2135

xref: https://docs.ci.openshift.org/docs/release-oversight/pull-request-testing/#payload-job

we just need to find a periodic job that will run your test. maybe some serial test from ?

so, overall:

  1. we add a new test to o/o. (this PR)
  2. we use the/payload-job-with-prs command to run the test with the o/k PR
  3. we make sure the test is green
  4. we merge the o/k PR
  5. we merge this PR

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 25, 2025

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

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/745c1ee0-0985-11f0-8a93-335e1efa7bdb-0

@jacobsee
Copy link
Member Author

@p0lyn0mial Addressed several things - however the wait for etcd to stabilize was a deliberate decision after a chat with @dusk125 however, so maybe we should bring that context to this thread here. The thinking was that it is also desirable to have a test for etcd's TLS 1.3 stability, and the test would have 90% the same code as this one (just with a different check in the middle), so we might we well ensure that both stabilize here to avoid duplicating an already-slow test.

@openshift-trt
Copy link

openshift-trt bot commented Mar 31, 2025

Job Failure Risk Analysis for sha: 76dc7ef

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling High
[sig-architecture] platform pods in ns/openshift-cluster-csi-drivers should not exit an excessive amount of times
This test has passed 99.98% of 6449 runs on release 4.19 [Overall] in the last week.

@jacobsee
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn openshift/kubernetes#2135

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 31, 2025

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

  • periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5ac351c0-0e39-11f0-9a0c-207cdc87222c-0

@wangke19
Copy link
Contributor

/test e2e-metal-ipi-ovn-ipv6

@wangke19
Copy link
Contributor

/cherry-pick release-4.20

@openshift-cherrypick-robot

@wangke19: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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.

@wangke19
Copy link
Contributor

/cherry-pick release-4.19

@openshift-cherrypick-robot

@wangke19: once the present PR merges, I will cherry-pick it on top of release-4.19 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.19

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.

@wangke19
Copy link
Contributor

/cherry-pick release-4.18

@openshift-cherrypick-robot

@wangke19: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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.

@petr-muller
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, jacobsee, petr-muller, sanchezl, wangke19

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:

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 Nov 24, 2025
@openshift-ci-robot
Copy link

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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-merge-bot openshift-merge-bot bot merged commit 66bb721 into openshift:main Nov 24, 2025
20 checks passed
@openshift-ci-robot
Copy link

@jacobsee: Jira Issue Verification Checks: Jira Issue OCPBUGS-64799
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-64799 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This PR:

  • Removes a skip on an existing TLS test - it appears to have been a setup issue
  • Adds a test for ensuring that components are properly listening for only the expected TLS version or higher.

cc: @dusk125

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-cherrypick-robot

@wangke19: new pull request created: #30522

In response to this:

/cherry-pick release-4.18

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-cherrypick-robot

@wangke19: new pull request created: #30523

In response to this:

/cherry-pick release-4.20

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-cherrypick-robot

@wangke19: new pull request created: #30524

In response to this:

/cherry-pick release-4.19

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 added a commit to neisw/origin that referenced this pull request Nov 25, 2025
wangke19 added a commit to wangke19/origin that referenced this pull request Nov 26, 2025
wangke19 added a commit to wangke19/origin that referenced this pull request Nov 26, 2025
This commit fixes two bugs in the TLS test that were causing failures:

1. Variable shadowing bug (line 145):
   - Changed `err := conn.Close()` to `closeErr := conn.Close()`
   - The original code shadowed the outer `err` variable, making the
     test logic confusing and error-prone
   - Now the test correctly checks the Dial error, not the Close error

2. Missing URL prefix stripping in cipher test (line 168-170):
   - Added `host := strings.TrimPrefix(oc.AdminConfig().Host, "https://")`
   - The cipher test was trying to dial with "https://..." prefix
   - tls.Dial expects "host:port" format, not a URL

3. Improved error handling in cipher test (line 172):
   - Properly capture and use closeErr instead of calling conn.Close()
     inline in the error message

These fixes address the test failures reported in:
periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-bm

Related: PR openshift#30533 (the revert), PR openshift#29611 (original implementation)
wangke19 added a commit to wangke19/origin that referenced this pull request Nov 27, 2025
This commit fixes two bugs in the TLS test that were causing failures:

1. Variable shadowing bug (line 145):
   - Changed `err := conn.Close()` to `closeErr := conn.Close()`
   - The original code shadowed the outer `err` variable, making the
     test logic confusing and error-prone
   - Now the test correctly checks the Dial error, not the Close error

2. Missing URL prefix stripping in cipher test (line 168-170):
   - Added `host := strings.TrimPrefix(oc.AdminConfig().Host, "https://")`
   - The cipher test was trying to dial with "https://..." prefix
   - tls.Dial expects "host:port" format, not a URL

3. Improved error handling in cipher test (line 172):
   - Properly capture and use closeErr instead of calling conn.Close()
     inline in the error message

These fixes address the test failures reported in:
periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-bm

Related: PR openshift#30533 (the revert), PR openshift#29611 (original implementation)
wangke19 added a commit to wangke19/origin that referenced this pull request Nov 28, 2025
This commit fixes two bugs in the TLS test that were causing failures:

1. Variable shadowing bug (line 145):
   - Changed `err := conn.Close()` to `closeErr := conn.Close()`
   - The original code shadowed the outer `err` variable, making the
     test logic confusing and error-prone
   - Now the test correctly checks the Dial error, not the Close error

2. Missing URL prefix stripping in cipher test (line 168-170):
   - Added `host := strings.TrimPrefix(oc.AdminConfig().Host, "https://")`
   - The cipher test was trying to dial with "https://..." prefix
   - tls.Dial expects "host:port" format, not a URL

3. Improved error handling in cipher test (line 172):
   - Properly capture and use closeErr instead of calling conn.Close()
     inline in the error message

These fixes address the test failures reported in:
periodic-ci-openshift-release-master-nightly-4.21-e2e-metal-ipi-ovn-bm

Related: PR openshift#30533 (the revert), PR openshift#29611 (original implementation)
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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.