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

Fix CSR validation failure for missing status conditions #1229

Merged
merged 1 commit into from Oct 27, 2022

Conversation

@mansikulkarni96 mansikulkarni96 marked this pull request as draft September 1, 2022 04:26
@mansikulkarni96
Copy link
Member Author

/test vsphere-e2e-operator

@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Sep 1, 2022
@mansikulkarni96
Copy link
Member Author

/retest

@mansikulkarni96 mansikulkarni96 changed the title [WIP] Fix failing CSR validation for pending CSR's [WIP] Fix failing CSR validation for pending CSR Oct 4, 2022
@mansikulkarni96 mansikulkarni96 changed the title [WIP] Fix failing CSR validation for pending CSR [WIP] Fix CSR validation failure for missing status conditions Oct 4, 2022
@mansikulkarni96 mansikulkarni96 changed the title [WIP] Fix CSR validation failure for missing status conditions Fix CSR validation failure for missing status conditions Oct 4, 2022
@@ -665,6 +665,10 @@ func (tc *testContext) findNodeCSRs(nodeName string) ([]certificates.Certificate
return nil, errors.Wrap(err, "unable to get CSR list")
}
for _, c := range csrs.Items {
// skip the CSR if it's status has not been reported
if len(c.Status.Conditions) == 0 {
Copy link
Contributor

@jrvaldes jrvaldes Oct 5, 2022

Choose a reason for hiding this comment

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

Conditions may be nil. Consider

if c.Status.Conditions == nil || len(c.Status.Conditions) == 0 {
   ...
}

@alinaryan
Copy link
Contributor

Thanks for working on this, LGTM so far. Will this be a temp workaround until we or the cloud team find a permanent fix?

@mansikulkarni96
Copy link
Member Author

Thanks for working on this, LGTM so far. Will this be a temp workaround until we or the cloud team find a permanent fix?

That is correct @alinaryan

@mansikulkarni96 mansikulkarni96 requested review from jrvaldes and removed request for sebsoto and aravindhp October 5, 2022 15:10
Copy link
Contributor

@aravindhp aravindhp left a comment

Choose a reason for hiding this comment

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

Thanks for fixing this, @mansikulkarni96

@@ -665,6 +665,10 @@ func (tc *testContext) findNodeCSRs(nodeName string) ([]certificates.Certificate
return nil, errors.Wrap(err, "unable to get CSR list")
}
for _, c := range csrs.Items {
// skip the CSR if it's status has not been reported
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add the suspected reason here and in the commit message.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 5, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aravindhp, mansikulkarni96

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 5, 2022
@jrvaldes
Copy link
Contributor

jrvaldes commented Oct 5, 2022

LGTM

@jrvaldes
Copy link
Contributor

jrvaldes commented Oct 5, 2022

/lgtm

@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 Oct 5, 2022
This commit aims to fix the issue with failing
CSR validation of CSR that have a missing
status condition.
In some cases, a CSR is left in pending state when a
new CSR is created for a node too quickly before
updating the status of the existing one.
Such a CSR cannot be approved but it does not affect
node configuration and is safe to be ignored.
@aravindhp
Copy link
Contributor

Blocked by OCPBUGS-2175

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 234a6cd and 1 for PR HEAD 3685963 in total

@JacobTanenbaum
Copy link
Contributor

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c6b350e and 0 for PR HEAD 3685963 in total

@openshift-ci-robot
Copy link

/hold

Revision 3685963 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 Oct 13, 2022
@JacobTanenbaum
Copy link
Contributor

/test azure-e2e-operator

@JacobTanenbaum
Copy link
Contributor

/retest ci/prow/aws-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2022

@JacobTanenbaum: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test aws-e2e-ccm-install
  • /test aws-e2e-operator
  • /test aws-e2e-upgrade
  • /test azure-e2e-operator
  • /test build
  • /test ci-index
  • /test gcp-e2e-operator
  • /test images
  • /test lint
  • /test unit
  • /test vsphere-e2e-operator
  • /test wicd-unit-vsphere

The following commands are available to trigger optional jobs:

  • /test azure-e2e-ccm-install
  • /test platform-none-vsphere-e2e-operator
  • /test vsphere-e2e-ccm-install

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

  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ccm-install
  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-upgrade
  • pull-ci-openshift-windows-machine-config-operator-master-azure-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-build
  • pull-ci-openshift-windows-machine-config-operator-master-ci-index
  • pull-ci-openshift-windows-machine-config-operator-master-gcp-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-images
  • pull-ci-openshift-windows-machine-config-operator-master-lint
  • pull-ci-openshift-windows-machine-config-operator-master-unit
  • pull-ci-openshift-windows-machine-config-operator-master-vsphere-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-wicd-unit-vsphere

In response to this:

/retest ci/prow/aws-e2e-operator

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.

@JacobTanenbaum
Copy link
Contributor

/test aws-e2e-operator

@patrickdillon
Copy link

/test gcp-e2e-operator

6 similar comments
@patrickdillon
Copy link

/test gcp-e2e-operator

@patrickdillon
Copy link

/test gcp-e2e-operator

@patrickdillon
Copy link

/test gcp-e2e-operator

@patrickdillon
Copy link

/test gcp-e2e-operator

@patrickdillon
Copy link

/test gcp-e2e-operator

@barbacbd
Copy link

/test gcp-e2e-operator

@mtnbikenc
Copy link
Member

/retest

@mtnbikenc
Copy link
Member

/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 Oct 26, 2022
@mtnbikenc
Copy link
Member

/retest

@mtnbikenc
Copy link
Member

@mansikulkarni96 the aws-e2e-operator job failed twice in the setup phase. Is this a new issue with AWS or a known flake?

@mansikulkarni96
Copy link
Member Author

There are issues creating EC2 instance, both jobs failed with different reasons though. Investigating.

@mansikulkarni96
Copy link
Member Author

/retest

@aravindhp
Copy link
Contributor

/override ci/prow/aws-e2e-operator

The test past previously we are now seeing a flake on AWS cluster installs.

level=error msg=Error: creating EC2 Instance: InvalidNetworkInterfaceID.NotFound

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 27, 2022

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

In response to this:

/override ci/prow/aws-e2e-operator

The test past previously we are now seeing a flake on AWS cluster installs.

level=error msg=Error: creating EC2 Instance: InvalidNetworkInterfaceID.NotFound

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-merge-robot openshift-merge-robot merged commit cd0c534 into openshift:master Oct 27, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 27, 2022

@mansikulkarni96: all tests passed!

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.

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

10 participants