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

Bug 1866480: pkg/cvo/status: Raise Operator leveling grace-period to 20 minutes #427

Conversation

wking
Copy link
Member

@wking wking commented Aug 5, 2020

Backporting #422 and, to avoid rebase conflicts, the doc-only #371 to 4.5.

Because every Failing=True condition should have a reason.

Also wordsmith the user-facing docs to replace "synchronize" with
"reconcile", because our merge logic is more nuanced than the complete
match "synchronize" implies for me.

The ClusterOperatorNotAvailable special casing landed with
convertErrorToProgressing in c2ac20f (status: Report the operators
that have not yet deployed, 2019-04-09, openshift#158).
Reduce false-positives when operators take a while to level (like the
machine-config operator, which has to roll the control plane
machines).  We may want to raise this further in the future, but baby
steps ;).

The previous 10-minute value is from c2ac20f (status: Report the
operators that have not yet deployed, 2019-04-09, openshift#158), which doesn't
make a case for that specific value.  So the bump is unlikely to break
anything unexpected.
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Aug 5, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: This pull request references Bugzilla bug 1866480, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1862524 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1862524 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

In response to this:

Bug 1866480: pkg/cvo/status: Raise Operator leveling grace-period to 20 minutes

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 5, 2020
Copy link
Member

@vrutkovs vrutkovs left a comment

Choose a reason for hiding this comment

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

lgtm in general, one (possible) nitpick

@@ -93,22 +93,22 @@ So the graph nodes are all parallelized with the by-number ordering flattened ou

For the usual reconciliation loop (neither an upgrade between releases nor a fresh install), the flattened graph is also randomly permuted to avoid hanging on ordering bugs.

## Synchronizing the graph
## Reconciling the graph
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
## Reconciling the graph
## Reconciling the cluster version

nit: "graph" sounds a bit ambiguous to me - I've immediately though of "updates graph" instead "manifests graph"

Copy link
Member Author

Choose a reason for hiding this comment

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

This is a backport PR. Drop an /lgtm, and then PR master with your change to "manifest graph", which sounds good to me.

@vrutkovs
Copy link
Member

vrutkovs commented Aug 6, 2020

/lgtm
/retest

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 6, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrutkovs, wking

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

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@jwforres jwforres added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 19, 2020
@openshift-merge-robot openshift-merge-robot merged commit b0f92e5 into openshift:release-4.5 Aug 19, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: All pull requests linked via external trackers have merged: openshift/cluster-version-operator#427. Bugzilla bug 1866480 has been moved to the MODIFIED state.

In response to this:

Bug 1866480: pkg/cvo/status: Raise Operator leveling grace-period to 20 minutes

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.

@wking wking deleted the raise-operator-leveling-timeout-4.5 branch August 25, 2020 22:02
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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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