Bug 1665238
Summary: | openshift-cluster-node-tuning-operator does not exist when using OCP images for the installer | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Hongkai Liu <hongkliu> |
Component: | Release | Assignee: | Tim Bielawa <tbielawa> |
Status: | CLOSED ERRATA | QA Contact: | Wei Sun <wsun> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | akamra, aos-bugs, hongkliu, jeder, jmencak, jokerman, mmccomas, smunilla, wking |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:41:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Hongkai Liu
2019-01-10 18:35:15 UTC
This should be assigned to the Release component [1]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1664984#c4 Not sure if it is expected: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-15-064327 True False 35m Cluster version is 4.0.0-0.nightly-2019-01-15-064327 $ oc get clusterversion version -o json | jq .status.desired { "payload": "registry.svc.ci.openshift.org/ocp/release@sha256:584f8f454184f6ece5679bf8103560f450e557d1d98711a4540d822c255fbeee", "version": "4.0.0-0.nightly-2019-01-15-064327" } $ oc project Using project "openshift-cluster-node-tuning-operator" on server "https://hongkliu-api.qe.devcluster.openshift.com:6443". $ oc get all NAME READY STATUS RESTARTS AGE pod/cluster-node-tuning-operator-7cc69776f4-pftpg 1/1 Running 0 40m pod/tuned-5sss6 1/1 Running 0 40m pod/tuned-68q8b 1/1 Running 0 40m pod/tuned-6wb4d 1/1 Running 0 38m pod/tuned-plwxh 1/1 Running 0 38m pod/tuned-znjr4 1/1 Running 0 38m pod/tuned-zq5c5 1/1 Running 0 40m NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/tuned 6 6 6 6 6 beta.kubernetes.io/os=linux 40m NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deployment.apps/cluster-node-tuning-operator 1 1 1 1 40m NAME DESIRED CURRENT READY AGE replicaset.apps/cluster-node-tuning-operator-7cc69776f4 1 1 1 40m I will test again when it moves to ON_QA. (In reply to Hongkai Liu from comment #6) > Not sure if it is expected: > > $ oc get clusterversion > NAME VERSION AVAILABLE PROGRESSING > SINCE STATUS > version 4.0.0-0.nightly-2019-01-15-064327 True False 35m > Cluster version is 4.0.0-0.nightly-2019-01-15-064327 > $ oc get clusterversion version -o json | jq .status.desired > { > "payload": > "registry.svc.ci.openshift.org/ocp/release@sha256: > 584f8f454184f6ece5679bf8103560f450e557d1d98711a4540d822c255fbeee", > "version": "4.0.0-0.nightly-2019-01-15-064327" > } > $ oc project > Using project "openshift-cluster-node-tuning-operator" on server > "https://hongkliu-api.qe.devcluster.openshift.com:6443". > $ oc get all > NAME READY STATUS > RESTARTS AGE > pod/cluster-node-tuning-operator-7cc69776f4-pftpg 1/1 Running 0 > 40m > pod/tuned-5sss6 1/1 Running 0 > 40m > pod/tuned-68q8b 1/1 Running 0 > 40m > pod/tuned-6wb4d 1/1 Running 0 > 38m > pod/tuned-plwxh 1/1 Running 0 > 38m > pod/tuned-znjr4 1/1 Running 0 > 38m > pod/tuned-zq5c5 1/1 Running 0 > 40m > > NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE > NODE SELECTOR AGE > daemonset.apps/tuned 6 6 6 6 6 > beta.kubernetes.io/os=linux 40m > > NAME DESIRED CURRENT > UP-TO-DATE AVAILABLE AGE > deployment.apps/cluster-node-tuning-operator 1 1 1 > 1 40m > > NAME DESIRED CURRENT > READY AGE > replicaset.apps/cluster-node-tuning-operator-7cc69776f4 1 1 > 1 40m > > > I will test again when it moves to ON_QA. If it is a 6 node OCP cluster, this looks good to me. Is there something you didn't expect? Ah, no. All good. I asked that because usually I would see Modified then see a fix. ^_^ I will test it again today. Thanks. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.1 True False 1h Cluster version is 4.0.0-0.1 $ oc get all -n openshift-cluster-node-tuning-operator NAME READY STATUS RESTARTS AGE pod/cluster-node-tuning-operator-6577b57d74-wktjj 1/1 Running 0 1h pod/tuned-27g57 1/1 Running 0 1h pod/tuned-g9g85 1/1 Running 0 1h pod/tuned-ggchv 1/1 Running 0 1h pod/tuned-kf7qd 1/1 Running 0 1h pod/tuned-p8nkr 1/1 Running 0 1h pod/tuned-r769k 1/1 Running 0 1h NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/tuned 6 6 6 6 6 beta.kubernetes.io/os=linux 1h NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deployment.apps/cluster-node-tuning-operator 1 1 1 1 1h NAME DESIRED CURRENT READY AGE replicaset.apps/cluster-node-tuning-operator-6577b57d74 1 1 1 1h Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |