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-21192: disable HTTP2 by default #849

Closed
wants to merge 1 commit into from

Conversation

cgoncalves
Copy link
Contributor

No description provided.

From docs: net/http/server.go

"[...] If TLSNextProto is not nil, HTTP/2 support
is not enabled automatically."
Server.TLSNextProto

Signed-off-by: Andrea Panattoni <[email protected]>
@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 Oct 24, 2023
@openshift-ci-robot
Copy link
Contributor

@cgoncalves: This pull request references Jira Issue OCPBUGS-21192, which is invalid:

  • expected dependent Jira Issue OCPBUGS-21211 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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.

In response to this:

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.

@openshift-ci openshift-ci bot requested review from s1061123 and SchSeba October 24, 2023 10:37
@bn222
Copy link
Contributor

bn222 commented Oct 25, 2023

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 25, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bn222, cgoncalves

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 Oct 25, 2023
@SchSeba
Copy link
Contributor

SchSeba commented Oct 26, 2023

/retest

@bn222
Copy link
Contributor

bn222 commented Oct 26, 2023

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 26, 2023
@cgoncalves
Copy link
Contributor Author

@zhaozhanqi please review.

@zhaozhanqi
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 14, 2023
@zhaozhanqi
Copy link

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@zhaozhanqi: This pull request references Jira Issue OCPBUGS-21192, which is invalid:

  • expected dependent Jira Issue OCPBUGS-21211 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

In response to this:

/jira refresh

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.

@zhaozhanqi
Copy link

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 15, 2023
@openshift-ci-robot
Copy link
Contributor

@zhaozhanqi: This pull request references Jira Issue OCPBUGS-21192, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-21211 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-21211 targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhaozhanqi

In response to this:

/jira refresh

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 15, 2023
@openshift-ci openshift-ci bot requested a review from zhaozhanqi November 15, 2023 07:01
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3b09c84 and 2 for PR HEAD 411ad74 in total

@cgoncalves
Copy link
Contributor Author

/retest-required

1 similar comment
@cgoncalves
Copy link
Contributor Author

/retest-required

zeeke added a commit to zeeke/sriov-network-operator-1 that referenced this pull request Nov 24, 2023
Using `@latest` for tools dependecies produces unrepeatable
builds which might break at any point in time.

This is particularly important when maintaining released versions
which need a backport fix.

Ref:
openshift/sriov-network-operator#849
Signed-off-by: Andrea Panattoni <[email protected]>
zeeke added a commit to zeeke/sriov-network-operator-1 that referenced this pull request Nov 24, 2023
Using `@latest` for tools dependecies produces unrepeatable
builds which might break at any point in time. This is
particularly important when maintaining released versions
which need a backport fix.

Note: At the moment is not possible to reference the package
`sigs.k8s.io/controller-runtime/tools/setup-envtest` with a specific
version:

```
go: sigs.k8s.io/controller-runtime/tools/[email protected]: module sigs.k8s.io/[email protected] found, but does not contain package sigs.k8s.io/controller-runtime/tools/setup-envtest
```

See kubernetes-sigs/kubebuilder#2480

Ref:
openshift/sriov-network-operator#849
Signed-off-by: Andrea Panattoni <[email protected]>
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 70bd2d4 and 1 for PR HEAD 411ad74 in total

Copy link
Contributor

openshift-ci bot commented Nov 27, 2023

@cgoncalves: 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-openstack-nfv 411ad74 link false /test e2e-openstack-nfv
ci/prow/pkg 411ad74 link true /test pkg
ci/prow/api 411ad74 link true /test api
ci/prow/controllers 411ad74 link true /test controllers

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.

@SchSeba
Copy link
Contributor

SchSeba commented Dec 21, 2023

Hi @cgoncalves there is a problem with one of the libs require a newer go version.

btw I think 4.11 is end of life no?

@cgoncalves
Copy link
Contributor Author

cgoncalves commented Dec 21, 2023

@SchSeba yeah. This is an issue that @zeeke fixed upstream: k8snetworkplumbingwg/sriov-network-operator#551. The next step would be to bring it downstream and to all supported releases.

OCP 4.11 is under maintenance support until February 10, 2024: https://access.redhat.com/support/policy/updates/openshift

zeeke added a commit to zeeke/sriov-network-operator that referenced this pull request Jan 2, 2024
Using `@latest` for tools dependecies produces unrepeatable
builds which might break at any point in time. This is
particularly important when maintaining released versions
which need a backport fix.

Note: At the moment is not possible to reference the package
`sigs.k8s.io/controller-runtime/tools/setup-envtest` with a specific
version:

```
go: sigs.k8s.io/controller-runtime/tools/[email protected]: module sigs.k8s.io/[email protected] found, but does not contain package sigs.k8s.io/controller-runtime/tools/setup-envtest
```

See kubernetes-sigs/kubebuilder#2480

Ref:
openshift#849
Signed-off-by: Andrea Panattoni <[email protected]>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/sriov-network-operator that referenced this pull request Jan 9, 2024
Using `@latest` for tools dependecies produces unrepeatable
builds which might break at any point in time. This is
particularly important when maintaining released versions
which need a backport fix.

Note: At the moment is not possible to reference the package
`sigs.k8s.io/controller-runtime/tools/setup-envtest` with a specific
version:

```
go: sigs.k8s.io/controller-runtime/tools/[email protected]: module sigs.k8s.io/[email protected] found, but does not contain package sigs.k8s.io/controller-runtime/tools/setup-envtest
```

See kubernetes-sigs/kubebuilder#2480

Ref:
openshift#849
Signed-off-by: Andrea Panattoni <[email protected]>
@cgoncalves
Copy link
Contributor Author

/close

4.11 CI is broken due to a known issue fixed in newer releases but it won't be backported. 4.11 is very soon at the end of life (February 10, 2024).

Copy link
Contributor

openshift-ci bot commented Jan 19, 2024

@cgoncalves: Closed this PR.

In response to this:

/close

4.11 CI is broken due to a known issue fixed in newer releases but it won't be backported. 4.11 is very soon at the end of life (February 10, 2024).

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.

@openshift-ci openshift-ci bot closed this Jan 19, 2024
@openshift-ci-robot
Copy link
Contributor

@cgoncalves: This pull request references Jira Issue OCPBUGS-21192. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

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.

SchSeba pushed a commit to SchSeba/sriov-network-operator that referenced this pull request May 7, 2024
Using `@latest` for tools dependecies produces unrepeatable
builds which might break at any point in time. This is
particularly important when maintaining released versions
which need a backport fix.

Note: At the moment is not possible to reference the package
`sigs.k8s.io/controller-runtime/tools/setup-envtest` with a specific
version:

```
go: sigs.k8s.io/controller-runtime/tools/[email protected]: module sigs.k8s.io/[email protected] found, but does not contain package sigs.k8s.io/controller-runtime/tools/setup-envtest
```

See kubernetes-sigs/kubebuilder#2480

Ref:
openshift#849
Signed-off-by: Andrea Panattoni <[email protected]>
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.