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

[AUTO][OLM][OCP-24829] Report Upgradeable in OLM ClusterOperators status #24352

Merged
merged 1 commit into from Jan 15, 2020

Conversation

bandrade
Copy link
Contributor

PR Created to automate test case: @ecordell @njhale @kevinrizza. please have a review. Thanks! cc: @cuipinghuo @scolange @chengzhang1016 @emmajiafan @jianzhangbjz @tbuskey

Success execution evidence:

 ./openshift-tests run all --dry-run | grep "Report Upgradeable" | ./openshift-tests run -f -

I1226 04:35:16.456207   24579 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
I1226 04:35:17.864259   24582 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
started: (0/1/1) "[Feature:Platform] OLM should Report Upgradeable in OLM ClusterOperators status [Suite:openshift/conformance/parallel]"

I1226 04:35:35.374320   25071 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
Dec 26 04:35:35.439: INFO: Waiting up to 30m0s for all (but 100) nodes to be schedulable
Dec 26 04:35:35.986: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Dec 26 04:35:36.570: INFO: 0 / 0 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Dec 26 04:35:36.570: INFO: expected 0 pod replicas in namespace 'kube-system', 0 are Running and Ready.
Dec 26 04:35:36.570: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start
Dec 26 04:35:36.769: INFO: e2e test version: v0.0.0-master+$Format:%h$
Dec 26 04:35:36.920: INFO: kube-apiserver version: v1.17.0
Dec 26 04:35:37.078: INFO: Cluster IP family: ipv4
[BeforeEach] [Top Level]
  /home/bandrade/go/src/github.com/openshift/origin/test/extended/util/test.go:60
[BeforeEach] [Feature:Platform] OLM should
  /home/bandrade/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:154
STEP: Creating a kubernetes client
[It] Report Upgradeable in OLM ClusterOperators status [Suite:openshift/conformance/parallel]
  /home/bandrade/go/src/github.com/openshift/origin/test/extended/operators/olm.go:134
Dec 26 04:35:37.109: INFO: Running 'oc --config=/home/bandrade/QE/ocp4-aws-ipi-vagrant-4.4/cluster/auth/kubeconfig get co operator-lifecycle-manager -o=jsonpath={range .status.conditions[*]}{.type}'
Dec 26 04:35:38.363: INFO: Running 'oc --config=/home/bandrade/QE/ocp4-aws-ipi-vagrant-4.4/cluster/auth/kubeconfig get co operator-lifecycle-manager-catalog -o=jsonpath={range .status.conditions[*]}{.type}'
Dec 26 04:35:39.333: INFO: Running 'oc --config=/home/bandrade/QE/ocp4-aws-ipi-vagrant-4.4/cluster/auth/kubeconfig get co operator-lifecycle-manager-packageserver -o=jsonpath={range .status.conditions[*]}{.type}'
[AfterEach] [Feature:Platform] OLM should
  /home/bandrade/go/src/github.com/openshift/origin/test/extended/util/client.go:120
[AfterEach] [Feature:Platform] OLM should
  /home/bandrade/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:155
Dec 26 04:35:40.152: INFO: Waiting up to 7m0s for all (but 100) nodes to be ready
Dec 26 04:35:40.560: INFO: Running AfterSuite actions on all nodes
Dec 26 04:35:40.560: INFO: Running AfterSuite actions on node 1

passed: (22.6s) 2019-12-26T07:35:40 "[Feature:Platform] OLM should Report Upgradeable in OLM ClusterOperators status [Suite:openshift/conformance/parallel]"

1 pass, 0 skip (22.6s)

@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Dec 26, 2019
@bandrade
Copy link
Contributor Author

/retest

@bandrade
Copy link
Contributor Author

/assign @jianzhangbjz

@bandrade
Copy link
Contributor Author

/retest

Copy link
Contributor

@njhale njhale left a comment

Choose a reason for hiding this comment

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

This seems like a general test that all SLOs must perform -- does that general test already exist somewhere?

@bandrade
Copy link
Contributor Author

bandrade commented Jan 7, 2020

/retest

1 similar comment
@bandrade
Copy link
Contributor Author

/retest

@bandrade
Copy link
Contributor Author

/retest

@njhale
Copy link
Contributor

njhale commented Jan 13, 2020

This looks good. I think my question from the last review still holds, but I don't think it should keep this PR from merging in the meantime.

/lgtm

@bandrade
Copy link
Contributor Author

@njhale Thanks, I did a quick search but I didn't find a generic test for this matter.

@bandrade
Copy link
Contributor Author

@shawn-hurley @bparees Could you help review it and give approve? Thanks!

@shawn-hurley
Copy link

oc get co operator-lifecycle-manager -o=jsonpath={range .status.conditions[*]}{.type}{' '}{.status}
zsh: no matches found: .status.conditions[*]}{.type}{ }{.status}

I am unable to get this to work locally, am I missing something?

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2020
@shawn-hurley
Copy link

Note to self, I got it to work once I put the quotes around it.

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2020
@bandrade
Copy link
Contributor Author

@shawn-hurley you may want to use oc get co operator-lifecycle-manager -o jsonpath="{range .status.conditions[*]}{.type}{' '}{.status}" . On framework it has some diferences due to escape chars.

@shawn-hurley
Copy link

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bandrade, njhale, shawn-hurley

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.

@openshift-bot
Copy link
Contributor

/retest

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

8 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot openshift-merge-robot merged commit bae2463 into openshift:master Jan 15, 2020
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/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants