Bug 1481550
| Summary: | [3.5]'oadm diagnostics NetworkCheck' timeout due to image 'openshift/diagnostics-deployer' pull failed | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaspreet Kaur <jkaur> | |
| Component: | Networking | Assignee: | Ravi Sankar <rpenta> | |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.5.0 | CC: | aos-bugs, bbennett, bmeng, cshereme, eparis, erich, fcami, fmarchio, jkaur, mluther, myllynen, rpenta, smunilla, zzhao | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | 3.5.z | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: A slow image pull makes the network diagnostics fail
Consequence: The network diagnostics fail to run
Fix: Increase the timeout for the image pull
Result: The diagnostics run in slow environments
|
Story Points: | --- | |
| Clone Of: | 1421643 | |||
| : | 1505898 (view as bug list) | Environment: | ||
| Last Closed: | 2017-12-07 07:11:23 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: | ||||
| Bug Depends On: | 1421643, 1481551 | |||
| Bug Blocks: | 1505898 | |||
|
Comment 1
Ravi Sankar
2017-08-17 16:27:55 UTC
Failed to verify this bug on v3.5.5.31.27 with error: when run 'oadm disgnostics NetworkCheck' , Check all test pods in the node will be 'Error' status. check the node logs: Sep 28 02:42:17 host-8-241-39.host.centralci.eng.rdu2.redhat.com dockerd-current[15883]: error: --deployment or OPENSHIFT_DEPLOYMENT_NAME is required Sep 28 02:42:17 host-8-241-39.host.centralci.eng.rdu2.redhat.com kernel: XFS (dm-20): Mounting V5 Filesystem Sep 28 02:42:17 host-8-241-39.host.centralci.eng.rdu2.redhat.com systemd-machined[18512]: Machine f043a75bd3e56d1c0caa0df9951e5442 terminated. Sep 28 02:42:17 host-8-241-39.host.centralci.eng.rdu2.redhat.com systemd[1]: Started docker container 9a6385c4bcc480639f11facb87864d0c04d9bbee1aa7dc6dca0da69058f5e573. Sep 28 02:42:17 host-8-241-39.host.centralci.eng.rdu2.redhat.com systemd[1]: Starti Verified this bug on v3.5.5.31.39 with rpm install this issue has been fixed 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/RHSA-2017:3389 Customer has re-opened the related case after updating the OCP version: "We have seen 2 new occurrences of the same problem both on production and development environments. In particular, on development note we now have OCP 3.4: oc v3.4.1.44 kubernetes v1.4.0+776c994" Apologies, I have by mistake cloned the wrong bugzilla. Setting status to NOTABUG |