Skip to content

status: Simplify operator not available status#190

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
smarterclayton:simplify_status
May 20, 2019
Merged

status: Simplify operator not available status#190
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
smarterclayton:simplify_status

Conversation

@smarterclayton
Copy link
Copy Markdown
Contributor

@smarterclayton smarterclayton commented May 19, 2019

In practice, the output of displaying version operands is redundant and our current use doesn't require it. Since the core output is

"we are going to X, these are the things not there yet"

also showing

"we are going to X, these are the things not there yet A-X,B-X,C-X"

makes it harder to understand what is going on.

Strip all sub version reporting from cluster operators, and in the future we can improve this if we have a use case.


Encountered while debugging failure output in upgrades - the key messages are always the actual Degraded conditition, and the extra versions are always variants of the operator version.

https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/1724/

Multiple errors are preventing progress:
* Cluster operator authentication is still updating: upgrading oauth-openshift from 4.2.0-0.ci-2019-05-18-031713_openshift to 4.2.0-0.ci-2019-05-18-224753_openshift
* Cluster operator cluster-autoscaler is still updating
* Cluster operator monitoring is still updating
* Cluster operator openshift-controller-manager is still updating
* Cluster operator service-catalog-controller-manager is still updating
* Could not update deployment "openshift-cloud-credential-operator/cloud-credential-operator" (93 of 350)
...

The first message is almost completely wasted space.

/cherrypick release-4.1

In practice, the output of displaying version operands is redundant
and our current use doesn't require it. Since the core output is

"we are going to X, these are the things not there yet"

also showing

"we are going to X, these are the things not there yet A-X,B-X,C-X"

makes it harder to understand what is going on.

Strip all sub version reporting from cluster operators, and in the
future we can improve this if we have a use case.
@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 19, 2019
@smarterclayton
Copy link
Copy Markdown
Contributor Author

/retest

@abhinavdahiya
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2019
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, smarterclayton

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:
  • OWNERS [abhinavdahiya,smarterclayton]

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

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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants