Skip to content

Conversation

@rfredette
Copy link
Contributor

Manual cherry pick of #930

rfredette added 2 commits May 23, 2023 11:30
Leave a stub of the CRL controller to clean up any existing configmaps.
The stub controller will need to be removed in a future release

Use cluster-wide proxy for CRL downloads when available

Add a test with several test cases to test CRL management
@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 23, 2023
@openshift-ci-robot
Copy link
Contributor

@rfredette: This pull request references Jira Issue OCPBUGS-13964, which is invalid:

  • expected dependent Jira Issue OCPBUGS-9464 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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.

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

Details

In response to this:

Manual cherry pick of #930

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 knobunc and miheer May 23, 2023 15:33
@rfredette
Copy link
Contributor Author

/assign @Miciah
/assign @frobware

Assuming the same reviewers as the parent PR

@rfredette
Copy link
Contributor Author

e2e-aws-operator won't pass until openshift/router#485 merges, but the other test failures should be unrelated.
/test e2e-azure-ovn
/test e2e-aws-ovn-single-node

@sjenning
Copy link
Contributor

/hold

see #930 (comment)

@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 23, 2023
@sferich888
Copy link

@sjenning does this still need to be on hold? or are we replacing this with openshift/router#485
cc: @rfredette

@rfredette
Copy link
Contributor Author

@sferich888 This PR is needed in addition to openshift/router#485.
As far as the hold goes, it should remain on hold until #939 merges, although that should be happening as soon as it makes it through CI.

@frobware
Copy link
Contributor

frobware commented Jun 2, 2023

    client_tls_test.go:1322: stdout:
    client_tls_test.go:1322: stderr:
        cat: /var/lib/haproxy/mtls/latest/crls.pem: No such file or directory

This will continue to fail until openshift/router#485 is merged.

@frobware
Copy link
Contributor

frobware commented Jun 2, 2023

/lgtm
/hold waiting for openshift/router#485

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

lihongan commented Jun 3, 2023

/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 Jun 3, 2023
@openshift-ci-robot
Copy link
Contributor

@lihongan: This pull request references Jira Issue OCPBUGS-13964, 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.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-9464 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-9464 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
  • bug has dependents

Requesting review from QA contact:
/cc @lihongan

Details

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 Jun 3, 2023
@openshift-ci openshift-ci bot requested a review from lihongan June 3, 2023 09:55
@Miciah
Copy link
Contributor

Miciah commented Jun 5, 2023

/approve

The purpose of this PR is to remove logic from cluster-ingress-operator that is being moved to the router with openshift/router#485. This logic is covered by E2E tests in cluster-ingress-operator. We have discussed and addressed implications for upgrades (operator as well as operand) and for the cluster-wide egress proxy (which the operator now configures the router to use, if applicable, to download CRLs). Engineering and QE have tested these changes extensively and have not found any other issues.

/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 Jun 5, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah

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 Jun 5, 2023
@lihongan
Copy link
Contributor

lihongan commented Jun 6, 2023

/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 Jun 6, 2023
@Miciah
Copy link
Contributor

Miciah commented Jun 6, 2023

/hold cancel
per #935 (comment) since openshift/router#485 merged.

@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 Jun 6, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 502e351 and 2 for PR HEAD 73a446d in total

@rfredette
Copy link
Contributor Author

Failed TestAWSELBConnectionIdleTimeout.
/retest

@frobware
Copy link
Contributor

frobware commented Jun 6, 2023

e2e-aws-operator - FAIL: TestAll/parallel/TestAWSELBConnectionIdleTimeout, which is bug https://issues.redhat.com/browse/OCPBUGS-13810.

Investigation for 13810 happening in: #940.

@frobware
Copy link
Contributor

frobware commented Jun 6, 2023

/retest-required

@frobware
Copy link
Contributor

frobware commented Jun 6, 2023

TestAWSELBConnectionIdleTimeout failed again.

/retest

@rfredette
Copy link
Contributor Author

Looking at the test history, all of the runs after the router PR merged only failed TestAWSELBConnectionIdleTimeout in the test suite. There were some must-gather failures as well, but they seem to be flakes.

@Miciah
Copy link
Contributor

Miciah commented Jun 6, 2023

/override ci/prow/e2e-aws-operator
based on #935 (comment).

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2023

@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-aws-operator

Details

In response to this:

/override ci/prow/e2e-aws-operator
based on #935 (comment).

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

openshift-ci bot commented Jun 6, 2023

@rfredette: The following test 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-aws-operator 73a446d link true /test e2e-aws-operator

Full PR test history. Your PR dashboard.

Details

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-merge-robot openshift-merge-robot merged commit 052f416 into openshift:release-4.13 Jun 6, 2023
@openshift-ci-robot
Copy link
Contributor

@rfredette: Jira Issue OCPBUGS-13964: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Manual cherry pick of #930

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.

@mffiedler
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jun 6, 2023
@mffiedler
Copy link

/remove-label qe-approved

removing label. incorrectly thought this was pre-merge tested

@openshift-ci openshift-ci bot removed the qe-approved Signifies that QE has signed off on this PR label Jun 6, 2023
@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.13.0-0.nightly-2023-06-06-122318

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/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.