Bug 1609149

Summary: [EehJwaEa] Should show the egressCIDRs info from client output of oc get hostsubnet
Product: OpenShift Container Platform Reporter: Meng Bo <bmeng>
Component: NetworkingAssignee: Dan Winship <danw>
Status: CLOSED ERRATA QA Contact: Meng Bo <bmeng>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, cdc, danw
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-11 07:22:24 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 Meng Bo 2018-07-27 07:02:43 UTC
Description of problem:
When get the hostsubnet info of the cluster, there is no egressCIDRs related values shown in the client output.

Version-Release number of selected component (if applicable):
v3.11.0-0.9.0

How reproducible:
always

Steps to Reproduce:
1. Setup ocp cluster with multitenant or networkpolicy plugin
2. Patch any of the node with egressCIDRs
# oc patch hostsubnet node1 -p '{"egressCIDRs":["10.1.1.0/24"]}'
3. Check the hostsubnet info via oc client
# oc get hostsubnet

Actual results:
There is no egressCIDRs related info printed to client output.

[root@ocp311-master ~]# oc get hostsubnet
NAME                        HOST                        HOST IP        SUBNET          EGRESS IPS
ocp311-master.bmeng.local   ocp311-master.bmeng.local   10.66.140.72   10.128.0.0/25   []
ocp311-node.bmeng.local     ocp311-node.bmeng.local     10.66.140.77   10.128.1.0/25   []

Expected results:
Should show the egressCIDRs value like the egressIPs

Additional info:
Should better put the egressCIDRs value in front of the egressIPS, since the value of egressIPs may be changed dynamically.

Comment 1 Dan Winship 2018-07-31 14:20:44 UTC
https://github.com/openshift/origin/pull/20486

Comment 3 Meng Bo 2018-09-12 08:40:04 UTC
Tested on v3.11.0-0.32.0

Issue has been fixed.

Comment 5 errata-xmlrpc 2018-10-11 07:22:24 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-2018:2652