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

pkg/cincinnati/cincinnati: Change "installed" -> "reconciling" for VersionNotFound #423

Merged

Conversation

wking
Copy link
Member

@wking wking commented Aug 2, 2020

When you initiate an update from A -> B, if B is not found in the current channel, the cluster would start reporting VersionNotFound after it's first attempt to retrieve recommended updates for B. That usually happens before the update completes, and the old "currently installed version" wasn't a very accurate description of B mid-update. The new wording relaxes our claim about the cluster state (maybe it has been reconciled, maybe not) and just talks about the version we're attempting to reconcile.

@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 2, 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

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2020
docs/user/status.md Outdated Show resolved Hide resolved
@LalatenduMohanty
Copy link
Member

/hold As I have a review comment.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 3, 2020
…rsionNotFound

When you initiate an update from A -> B, if B is not found in the
current channel, the cluster would start reporting VersionNotFound
after it's first attempt to retrieve recommended updates for B.  That
usually happens before the update completes, and the old "currently
installed version" wasn't a very accurate description of B mid-update.
The new wording relaxes our claim about the cluster state (maybe it
has been reconciled, maybe not) and just talks about the version we're
attempting to reconcile.

The addition of "cluster" is intended to be more explicit about which
version we are discussing [1].  Personally I think the occurence
within the CVO repo's docs and ClusterVersion condition messages is
sufficient context, so I'm agnostic about the additional "cluster".

[1]: openshift#423 (comment)
@wking wking force-pushed the clarify-currently-installed branch from 9f15457 to ea6899a Compare August 4, 2020 15:09
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2020
Copy link
Member

@LalatenduMohanty LalatenduMohanty left a comment

Choose a reason for hiding this comment

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

/lgtm

@LalatenduMohanty
Copy link
Member

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 4, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, 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:
  • OWNERS [LalatenduMohanty,vrutkovs,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2020
@openshift-merge-robot openshift-merge-robot merged commit d2fc678 into openshift:master Aug 4, 2020
@wking wking deleted the clarify-currently-installed branch August 4, 2020 21:20
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.

5 participants