Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1481550 - [3.5]'oadm diagnostics NetworkCheck' timeout due to image 'openshift/diagnostics-deployer' pull failed
[3.5]'oadm diagnostics NetworkCheck' timeout due to image 'openshift/diagnost...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.5.0
All All
high Severity high
: ---
: 3.5.z
Assigned To: Ravi Sankar
Meng Bo
: Reopened
Depends On: 1421643 1481551
Blocks: 1505898
  Show dependency tree / graph
 
Reported: 2017-08-15 01:09 EDT by Jaspreet Kaur
Modified: 2018-07-10 12:39 EDT (History)
14 users (show)

See Also:
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 02:11:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Origin (Github) 12982 None None None 2017-08-15 01:09 EDT
Red Hat Product Errata RHSA-2017:3389 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise security, bug fix, and enhancement update 2017-12-07 07:09:10 EST

  None (edit)
Comment 1 Ravi Sankar 2017-08-17 12:27:55 EDT 
OSE enterprise-3.5 PR: https://github.com/openshift/ose/pull/846
Comment 6 zhaozhanqi 2017-09-28 02:46:28 EDT 
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
Comment 7 Ravi Sankar 2017-10-16 20:22:52 EDT 
Fixed in https://github.com/openshift/ose/pull/905
Comment 10 zhaozhanqi 2017-10-25 07:48:08 EDT 
Verified this bug on v3.5.5.31.39 with rpm install

this issue has been fixed
Comment 13 errata-xmlrpc 2017-12-07 02:11:23 EST 
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
Comment 14 Francesco Marchioni 2018-01-24 11:26:33 EST 
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"
Comment 15 Francesco Marchioni 2018-01-24 11:34:14 EST 
Apologies, I have by mistake cloned the wrong bugzilla. Setting status to NOTABUG
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.