Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-29373: test/extended/router/http2: Use unique certs #28757

Conversation

Miciah
Copy link
Contributor

@Miciah Miciah commented Apr 30, 2024

Use a unique certificate for each route in the "The HAProxy router should pass the http2 tests" extended test.

To fix OCPBUGS-29373, OpenShift router will be changed to configure HAProxy not to negotiate HTTP/2 with TLS ALPN for routes that share certificates. This change in the router causes the aforesaid extended test to fail because it uses the same certificate for two test routes that are used to verify HTTP/2 compliance.

After this PR, the extended tests should pass with the router change.

Use a unique certificate for each route in the "The HAProxy router should
pass the http2 tests" extended test.

To fix OCPBUGS-29373, OpenShift router will be changed to configure HAProxy
not to negotiate HTTP/2 with TLS ALPN for routes that share certificates.
This change in the router causes the aforesaid extended test to fail
because it uses the same certificate for two test routes that are used to
verify HTTP/2 compliance.

After this commit, the extended tests should pass with the router change.

This commit is related to OCPBUGS-29373.

https://issues.redhat.com/browse/OCPBUGS-29373

* test/extended/router/http2.go: Generate and use a unique certificate-key
pair for each route.
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 30, 2024
@openshift-ci-robot
Copy link

@Miciah: This pull request references Jira Issue OCPBUGS-29373, which is valid.

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

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Use a unique certificate for each route in the "The HAProxy router should pass the http2 tests" extended test.

To fix OCPBUGS-29373, OpenShift router will be changed to configure HAProxy not to negotiate HTTP/2 with TLS ALPN for routes that share certificates. This change in the router causes the aforesaid extended test to fail because it uses the same certificate for two test routes that are used to verify HTTP/2 compliance.

After this PR, the extended tests should pass with the router change.

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 a review from ShudiLi April 30, 2024 13:48
@openshift-ci openshift-ci bot requested review from knobunc and miheer April 30, 2024 13:52
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2024
@frobware
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 30, 2024
Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: frobware, Miciah

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

/retest-required

Remaining retests: 0 against base HEAD 221cc88 and 2 for PR HEAD 1f14f77 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 226191c and 1 for PR HEAD 1f14f77 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 07e13e2 and 0 for PR HEAD 1f14f77 in total

@openshift-ci-robot
Copy link

/hold

Revision 1f14f77 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 1, 2024
@frobware
Copy link
Contributor

frobware commented May 2, 2024

/retest

@frobware
Copy link
Contributor

frobware commented May 2, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 2, 2024
Copy link
Contributor

openshift-ci bot commented May 2, 2024

@Miciah: The following tests 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-gcp-csi 1f14f77 link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node-upgrade 1f14f77 link false /test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

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

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 1f14f77

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-csi IncompleteTests
Tests for this run (25) are below the historical average (647): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-merge-bot openshift-merge-bot bot merged commit e4b8310 into openshift:master May 2, 2024
20 of 22 checks passed
@openshift-ci-robot
Copy link

@Miciah: Jira Issue OCPBUGS-29373: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-29373 has not been moved to the MODIFIED state.

In response to this:

Use a unique certificate for each route in the "The HAProxy router should pass the http2 tests" extended test.

To fix OCPBUGS-29373, OpenShift router will be changed to configure HAProxy not to negotiate HTTP/2 with TLS ALPN for routes that share certificates. This change in the router causes the aforesaid extended test to fail because it uses the same certificate for two test routes that are used to verify HTTP/2 compliance.

After this PR, the extended tests should pass with the router change.

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202405022319.p0.ge4b8310.assembly.stream.el9 for distgit openshift-enterprise-tests.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-05-04-214435

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-critical Referenced Jira bug's severity is critical 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants