Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1707749

Summary: egressip column cannot be shown for hostsubnet and netnamespaces in CLI
Product: OpenShift Container Platform Reporter: zhaozhanqi <zzhao>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: low CC: aos-bugs
Version: 4.1.0   
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:28:32 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 zhaozhanqi 2019-05-08 09:07:36 UTC
Description of problem:
No 'egressip' column when run 'oc get hostsubnet' or 'oc get netnamespaces'

Version-Release number of selected component (if applicable):
4.1.0-0.nightly-2019-05-07-233329

How reproducible:
always

Steps to Reproduce:
1. oc get hostsubnet 
2. oc get netnamespaces
3. 

Actual results:

no egressip column

Expected results:

egressip should be shown.

Additional info:

The egressip function works well. just the client side cannot be shown the egressip, it's not convenient.

I guess we just add one column in crd. eg:

additionalPrinterColumns:
  - JSONPath: .host
    description: The name of the node
    name: Host
    type: string
  - JSONPath: .hostIP
    description: The IP address to be used as a VTEP by other nodes in the overlay
      network
    name: Host IP
    type: string
  - JSONPath: .subnet
    description: The CIDR range of the overlay network assigned to the node for its
      pods
    name: Subnet
    type: string
  conversion:
    strategy: None
  group: network.openshift.io
  names:

Comment 1 Casey Callendrello 2019-05-08 09:49:14 UTC
Strikes me as an RFE, but a good idea.

Comment 2 Casey Callendrello 2019-07-15 20:12:28 UTC
Oh duh, I misunderstood this bug. Yes, we should update the CRD to include these columns.

The CRDs defined in openshift-sdn should have, as much as possible, the same printer columns as they did in 3.11.

Comment 3 Alexander Constantinescu 2019-07-23 12:40:23 UTC
Hi

A PR addressing this has been merged: https://github.com/openshift/cluster-network-operator/pull/241

Best regards
Alexander

Comment 5 zhaozhanqi 2019-07-24 07:31:10 UTC
Verified this bug on 4.2.0-0.nightly-2019-07-24-000310

The egress ip can be shown.

oc get hostsubnet ip-10-0-141-238.ap-northeast-1.compute.internal -o wide
NAME                                              HOST                                              HOST IP        SUBNET          EGRESS CIDRS       EGRESS IPS
ip-10-0-141-238.ap-northeast-1.compute.internal   ip-10-0-141-238.ap-northeast-1.compute.internal   10.0.141.238   10.128.2.0/23   [10.66.146.1/24]   [10.66.146.100]

$ oc get netnamespaces z1
NAME   NETID      EGRESS IPS
z1     16032885   [10.66.146.100]

Comment 6 errata-xmlrpc 2019-10-16 06:28:32 UTC
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:2922