Skip to content

Change Failed to Degraded#165

Merged
openshift-merge-robot merged 4 commits intoopenshift:masterfrom
eparis:failed-to-degraded
Apr 18, 2019
Merged

Change Failed to Degraded#165
openshift-merge-robot merged 4 commits intoopenshift:masterfrom
eparis:failed-to-degraded

Conversation

@eparis
Copy link
Copy Markdown
Member

@eparis eparis commented Apr 17, 2019

No description provided.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 17, 2019
@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 17, 2019
@eparis
Copy link
Copy Markdown
Member Author

eparis commented Apr 17, 2019

Based on: openshift/api#287

@eparis eparis force-pushed the failed-to-degraded branch 10 times, most recently from f1a8c6c to 54ed420 Compare April 17, 2019 14:49
@eparis eparis changed the title [wip] Change Failed to Degraded Change Failed to Degraded Apr 17, 2019
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 17, 2019
@eparis
Copy link
Copy Markdown
Member Author

eparis commented Apr 17, 2019

docs PR: #161

@eparis
Copy link
Copy Markdown
Member Author

eparis commented Apr 17, 2019

see: openshift/api#287

Comment thread pkg/cvo/internal/operatorstatus.go Outdated
Comment thread pkg/cvo/internal/operatorstatus.go
Comment thread hack/test-integration.sh Outdated
@smarterclayton smarterclayton self-assigned this Apr 17, 2019
Copy link
Copy Markdown
Contributor

@smarterclayton smarterclayton left a comment

Choose a reason for hiding this comment

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

What did you use to update? make vendor?

@eparis eparis force-pushed the failed-to-degraded branch from 54ed420 to 51d66be Compare April 17, 2019 17:30
@eparis
Copy link
Copy Markdown
Member Author

eparis commented Apr 17, 2019

Updating vendor was via:
dep ensure update github.com/openshift/client-go
dep ensure
You definitely don't want to just do dep ensure update
There doesn't appear to be a make vendor

@eparis eparis force-pushed the failed-to-degraded branch from 51d66be to 7e7f31a Compare April 17, 2019 17:47
This is so we can use --args --alsologtostderr for all integration tests
@eparis eparis force-pushed the failed-to-degraded branch from 7e7f31a to 73179c1 Compare April 17, 2019 21:07
@eparis
Copy link
Copy Markdown
Member Author

eparis commented Apr 17, 2019

/retest

@smarterclayton
Copy link
Copy Markdown
Contributor

This looks ok to me but want @abhinavdahiya to take a look if he can tomorrow.

@smarterclayton
Copy link
Copy Markdown
Contributor

/test all

@smarterclayton
Copy link
Copy Markdown
Contributor

Ok, will deal with fallout in separate issues

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eparis, 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:

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

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eparis, 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:

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 18, 2019
@openshift-merge-robot openshift-merge-robot merged commit 939e6d9 into openshift:master Apr 18, 2019
wking added a commit to wking/cluster-version-operator that referenced this pull request Apr 22, 2019
…ing -> Degraded

Fix [1]:

  $ oc get clusteroperators kube-apiserver
  NAME             VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
  kube-apiserver   4.1.0-0.nightly-2019-04-22-005054   True        False                   20m

when the ClusterOperator only sets Degraded.  This should have
happened in 94c4e57 (Use the new degraded condition is available,
2019-04-16, openshift#165).

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1702087
wking added a commit to wking/cluster-version-operator that referenced this pull request Apr 23, 2019
…Degraded

Fix [1]:

  $ oc get clusteroperators kube-apiserver
  NAME             VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
  kube-apiserver   4.1.0-0.nightly-2019-04-22-005054   True        False                   20m

when the ClusterOperator only sets Degraded.  This should have
happened in 94c4e57 (Use the new degraded condition is available,
2019-04-16, openshift#165).  There may be some JSONPath syntax to collapse both
into a single column:

  .status.conditions[?(@.type IN ["Degraded", "Failing"])].status

but if it exists, I haven't discovered it.  We can drop the Failing
column once all the operators have migrated.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1702087
wking added a commit to wking/cluster-version-operator that referenced this pull request Apr 23, 2019
…aded -> Failing

Fix [1]:

  $ oc get clusteroperators kube-apiserver
  NAME             VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
  kube-apiserver   4.1.0-0.nightly-2019-04-22-005054   True        False                   20m

when the ClusterOperator only sets Degraded.  This should have
happened in 94c4e57 (Use the new degraded condition is available,
2019-04-16, openshift#165).  There may be some JSONPath syntax to collapse both
into a single column:

  .status.conditions[?(@.type IN ["Degraded", "Failing"])].status

but if it exists, I haven't discovered it.  We're hopefully going to
fix the operators that are still using Failing soon, so just skip to
the new field without supporting both [2].

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1702087
[2]: openshift#172 (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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants