Bug 1447250
Summary: | oc rollout status --request-timeout=0 times out | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Paul Dwyer <pdwyer> |
Component: | oc | Assignee: | Tomáš Nožička <tnozicka> |
Status: | CLOSED ERRATA | QA Contact: | zhou ying <yinzhou> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.0 | CC: | aos-bugs, decarr, ffranz, hgomes, jokerman, mfojtik, mmccomas, pdwyer, sttts, tcarlin, tnozicka, travi, xxia |
Target Milestone: | --- | Keywords: | UpcomingRelease |
Target Release: | 4.1.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
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:40:18 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
Paul Dwyer
2017-05-02 08:41:01 UTC
fabiano - see related cli issue here: https://github.com/kubernetes/kubernetes/issues/40224 Moving this to 3.11 release as the changes in upstream are significant and we unlikely be able to backport this to 3.10. Also this is not a regression, as this had been broken since 3.4. apimachinery fixed with: https://github.com/kubernetes/kubernetes/pull/66971 upstream fix for rollout status: https://github.com/kubernetes/kubernetes/pull/67817 upstream PR is merged, this will come with 1.12 rebase Confirmed with latest origin, can't reproduce it : [root@dhcp-140-138 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.alpha-2019-02-11-201342 True False 5m10s Cluster version is 4.0.0-0.alpha-2019-02-11-201342 [root@dhcp-140-138 ~]# oc rollout status --request-timeout=0 dc/nodejs-mongodb-example Deployment config "nodejs-mongodb-example" waiting on image update W0212 16:26:05.047455 8251 reflector.go:270] k8s.io/client-go/tools/watch/informerwatcher.go:110: watch of *unstructured.Unstructured ended with: very short watch: k8s.io/client-go/tools/watch/informerwatcher.go:110: Unexpected watch close - watch lasted less than a second and no items received Deployment config "nodejs-mongodb-example" waiting on image update W0212 16:40:19.304936 8251 reflector.go:270] k8s.io/client-go/tools/watch/informerwatcher.go:110: watch of *unstructured.Unstructured ended with: very short watch: k8s.io/client-go/tools/watch/informerwatcher.go:110: Unexpected watch close - watch lasted less than a second and no items received Deployment config "nodejs-mongodb-example" waiting on image update Waiting for latest deployment config spec to be observed by the controller loop... Waiting for rollout to finish: 0 out of 1 new replicas have been updated... Waiting for rollout to finish: 0 out of 1 new replicas have been updated... Waiting for rollout to finish: 0 out of 1 new replicas have been updated... Waiting for rollout to finish: 0 of 1 updated replicas are available... Waiting for latest deployment config spec to be observed by the controller loop... replication controller "nodejs-mongodb-example-1" successfully rolled out [root@dhcp-140-138 ~]# oc get po NAME READY STATUS RESTARTS AGE jenkins-1-5xx4z 1/1 Running 0 86m jenkins-1-deploy 0/1 Completed 0 87m mongodb-1-deploy 0/1 Completed 0 37m mongodb-1-stgkq 1/1 Running 0 37m nodejs-mongodb-example-1-2mjts 1/1 Running 0 90s nodejs-mongodb-example-1-build 0/1 Completed 0 3m2s nodejs-mongodb-example-1-deploy 0/1 Completed 0 99s 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 |