Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1509661 - show namespace in oc adm manage-node --list-pods
show namespace in oc adm manage-node --list-pods
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
3.7.0
Unspecified Unspecified
unspecified Severity medium
: ---
: 3.8.0
Assigned To: Juan Vallejo
Xingxing Xia
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-05 08:49 EST by Eric Paris
Modified: 2018-03-28 10:10 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:09:47 EDT
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:10 EDT

  None (edit)
Description Eric Paris 2017-11-05 08:49:08 EST
The default columns displayed for
oc adm manage-node --list-pods

Should be the same as the default columns for something like
oc get pod --all-namespaces

Today you get a list of pod names but when looking at a node what namespace those pods are in is unknown. Yes, this can be managed using a template, or custom columns, or any other sort of additional human intervention, but normally if I am trying to figure out what pods are on a node its because I probably want to dig deeper into one of those pods. And doing that requires the namespace.
Comment 1 Juan Vallejo 2017-11-08 17:51:25 EST
Origin PR: https://github.com/openshift/origin/pull/17241
Comment 2 Xingxing Xia 2017-11-15 03:50:54 EST
Checked in latest version v3.7.8, it does not include the PR per https://url.corp.redhat.com/3a0e336 (Red Hat internal)
Saw Target Release is 3.8.0, will the PR go to v3.7? If no, can you move bug to MODIFIED? Then it will be tested when v3.8 is available
Comment 4 XiaochuanWang 2018-01-03 02:58:15 EST
Verified on oc v3.9.0-0.9.0 (kubernetes v1.8.1+0d5291c) as below:

# oc adm manage-node --list-pods x.x.x.x

Listing matched pods on node: x.x.x.x

NAMESPACE                           NAME                              READY     STATUS      RESTARTS   AGE
default                             docker-registry-1-rdk2r           1/1       Running     0          7d
...

Default columns are same as below
# oc get pod --all-namespaces
NAMESPACE                           NAME                              READY     STATUS      RESTARTS   AGE
default                             docker-registry-1-rdk2r           1/1       Running     0          7d
...
Comment 7 errata-xmlrpc 2018-03-28 10:09:47 EDT
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-2018:0489

Note You need to log in before you can comment on or make changes to this bug.