Bug 1506343 - oadm diagnostics NetworkCheck fails with pod error saying OPENSHIFT_DEPLOYMENT_NAME is required
Summary: oadm diagnostics NetworkCheck fails with pod error saying OPENSHIFT_DEPLOYME...
Keywords:
Status: CLOSED DUPLICATE of bug 1505898
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ravi Sankar
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-25 18:46 UTC by Ryan Howe
Modified: 2017-10-31 19:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-31 19:20:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ryan Howe 2017-10-25 18:46:29 UTC 
Description of problem:

The diagnostics network check fails using the ose-deployer pods due to not passing OPENSHIFT_DEPLOYMENT_NAME. 


Version-Release number of selected component (if applicable):
> openshift version
openshift v3.6.173.0.21
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

How reproducible:
100% 

Steps to Reproduce:
1.  oadm diagnostics --diaglevel=0  NetworkCheck --config=/etc/origin/master/admin.kubeconfig

Actual results:
ERROR: [DNet2005 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/run_pod.go:119]
       Setting up test environment for network diagnostics failed: Failed to run network diags test pod and service: Failed to run network diags test pods, failed: 4, total: 4


Expected results:

Not to fail if network is healthy 


Additional info:

> oc logs -n network-diag-ns-qpgl9  network-diag-test-pod-xqg6j  
  error: --deployment or OPENSHIFT_DEPLOYMENT_NAME is required
Comment 1 Ravi Sankar 2017-10-31 19:20:41 UTC 

*** This bug has been marked as a duplicate of bug 1505898 ***
Note You need to log in before you can comment on or make changes to this bug.