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-17199: Separated the revision stability check from the bootstrap completeness check #1360

Conversation

jubittajohn
Copy link
Contributor

@jubittajohn jubittajohn commented Oct 24, 2024

Separated the revision stability check from the bootstrap completeness check to ensure the revision stability check is only called from controllers that need them.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Oct 24, 2024
@openshift-ci-robot
Copy link

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

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

Requesting review from QA contact:
/cc @sandeepknd

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 openshift-eng/jira-lifecycle-plugin repository.

@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 Oct 24, 2024
@openshift-ci openshift-ci bot requested a review from sandeepknd October 24, 2024 19:13
@jubittajohn
Copy link
Contributor Author

/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-ipv6

@openshift-ci openshift-ci bot requested review from Elbehery and hasbro17 October 24, 2024 19:13
Comment on lines 162 to 167
if shouldRunRevisionStabilityCheck {
_, status, _, err := staticPodClient.GetStaticPodOperatorState()
if err != nil {
return false, fmt.Errorf("failed to get static pod operator state: %w", err)
}
if status.LatestAvailableRevision == 0 {
Copy link
Contributor

@tjungblu tjungblu Oct 30, 2024

Choose a reason for hiding this comment

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

I would start to split out those functions and have one for "IsBootstrapComplete" and one for "IsRevisionStable".

etcdendpointscontroller.go and the check above can then just use the IsRevisionStable function alongside the IsBootstrapComplete - the others can stay as they are

@jubittajohn jubittajohn changed the title OCPBUGS-17199: WIP: Added a function parameter to IsBootstrapComplete to determine whether to run the revision stability check OCPBUGS-17199: WIP: Separated the revision stability check from the bootstrap completeness check Oct 31, 2024
@openshift-ci-robot
Copy link

@jubittajohn: This pull request references Jira Issue OCPBUGS-17199, which is valid.

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

Requesting review from QA contact:
/cc @sandeepknd

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

In response to this:

Separated the revision stability check from the bootstrap completeness check to only call the revision stability check from controllers that need them.

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.

@jubittajohn jubittajohn force-pushed the enable-safe-member-deletion-during-revision-rollout branch 2 times, most recently from 0e12674 to 7976cdf Compare October 31, 2024 16:13
@jubittajohn
Copy link
Contributor Author

/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-ipv6

@jubittajohn jubittajohn force-pushed the enable-safe-member-deletion-during-revision-rollout branch from 63216b4 to c237575 Compare November 4, 2024 03:07
@jubittajohn
Copy link
Contributor Author

/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-ipv6

@jubittajohn
Copy link
Contributor Author

/test unit

@jubittajohn
Copy link
Contributor Author

/test e2e-aws-ovn-etcd-scaling

@jubittajohn
Copy link
Contributor Author

/test e2e-aws-ovn-single-node

@jubittajohn
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.18-periodics-e2e-aws 10

Copy link
Contributor

openshift-ci bot commented Nov 4, 2024

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

  • periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.18-periodics-e2e-aws

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/214bf780-9acb-11ef-8530-2536f6b242fa-0

@jubittajohn
Copy link
Contributor Author

/retest

@jubittajohn jubittajohn changed the title OCPBUGS-17199: WIP: Separated the revision stability check from the bootstrap completeness check OCPBUGS-17199: Separated the revision stability check from the bootstrap completeness check Nov 4, 2024
@jubittajohn jubittajohn force-pushed the enable-safe-member-deletion-during-revision-rollout branch from 28397e5 to 7522927 Compare November 4, 2024 21:01
@jubittajohn
Copy link
Contributor Author

/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-ipv6

@jubittajohn
Copy link
Contributor Author

/retest-required

@jubittajohn jubittajohn requested a review from tjungblu November 5, 2024 05:14
}

// while bootstrapping and when revision is stabilising, scaling should be considered safe always
if !bootstrapComplete || !revisionStable {
Copy link
Contributor

Choose a reason for hiding this comment

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

I know it's not an expensive call, but feel free to early exit on the first check already. There's no sense in checking revision stability if the bootstrap is not completed yet

…s check

Signed-off-by: jubittajohn <jujohn@redhat.com>
@jubittajohn jubittajohn force-pushed the enable-safe-member-deletion-during-revision-rollout branch from cd75e92 to 8ffe961 Compare November 6, 2024 16:43
@jubittajohn
Copy link
Contributor Author

/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-ipv6

@tjungblu
Copy link
Contributor

tjungblu commented Nov 6, 2024

/lgtm
/hold

@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 Nov 6, 2024
Copy link
Contributor

openshift-ci bot commented Nov 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jubittajohn, tjungblu

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 6, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 6, 2024
Copy link
Contributor

openshift-ci bot commented Nov 6, 2024

@jubittajohn: 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-metal-ovn-ha-cert-rotation-shutdown 8ffe961 link false /test e2e-metal-ovn-ha-cert-rotation-shutdown
ci/prow/e2e-aws-etcd-certrotation 8ffe961 link false /test e2e-aws-etcd-certrotation
ci/prow/e2e-aws-etcd-recovery 8ffe961 link false /test e2e-aws-etcd-recovery
ci/prow/e2e-metal-ovn-sno-cert-rotation-shutdown 8ffe961 link false /test e2e-metal-ovn-sno-cert-rotation-shutdown

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

@jubittajohn
Copy link
Contributor Author

/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 Nov 7, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7d0e358 into openshift:master Nov 7, 2024
15 of 19 checks passed
@openshift-ci-robot
Copy link

@jubittajohn: Jira Issue OCPBUGS-17199: All pull requests linked via external trackers have merged:

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

In response to this:

Separated the revision stability check from the bootstrap completeness check to ensure the revision stability check is only called from controllers that need them.

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]

Distgit: cluster-etcd-operator
This PR has been included in build cluster-etcd-operator-container-v4.18.0-202411070737.p0.g7d0e358.assembly.stream.el9.
All builds following this will include this PR.

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-moderate Referenced Jira bug's severity is moderate 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.

4 participants