Bug 1885940

Summary:	kuryr/demo image ping not working
Product:	OpenShift Container Platform	Reporter:	rlobillo
Component:	Networking	Assignee:	Maysa Macedo <mdemaced>
Networking sub component:	kuryr	QA Contact:	GenadiC <gcheresh>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	mdemaced
Version:	4.6	Keywords:	TestBlocker
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:23:22 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 rlobillo 2020-10-07 10:22:30 UTC

Description of problem:

kuryr-tempest-plugin tests are failing because pods based on kuryr/demo image have a problem running ping command:

$ oc get pods -o wide
NAME                  READY   STATUS    RESTARTS   AGE   IP              NODE                          NOMINATED NODE   READINESS GATES
kuryr-pod-786941607   1/1     Running   0          15m   10.128.25.159   ostest-7brpn-worker-0-p5nlz   <none>           <none>
kuryr-pod-822586474   1/1     Running   0          15m   10.128.25.250   ostest-7brpn-worker-0-2xm2p   <none>           <none>
$ oc exec -it kuryr-pod-786941607 /bin/sh                                                        kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
~ $ ping 10.128.25.250
PING 10.128.25.250 (10.128.25.250): 56 data bytes
ping: permission denied (are you root?)
~ $ 

This behaviour is not observed for the exact imageID on OCP4.5.


Version-Release number of selected component (if applicable): 4.6.0-0.nightly-2020-10-07-022140


How reproducible:


Steps to Reproduce:
1. Install latest OCP4.6
2. Run kuryr-tempest-plugin tests
3.

Actual results: All connectivity tests are failing.


Expected results: Connectivity tests passing.


Additional info:

Comment 1 Luis Tomas Bolivar 2020-10-07 11:37:07 UTC

This is related to the kuryr/demo image, not related to Kuryr or OCP

Comment 2 Maysa Macedo 2020-10-19 07:44:54 UTC

The kuryr/demo image is already updated with the fix.

Comment 3 rlobillo 2020-10-20 14:30:27 UTC

Verified on OCP4.6, running tempest that is fetching the latest kuryr/demo image:

(shiftstack) [stack@undercloud-0 ~]$ oc get pods                                                                                                                                              
NAME                   READY   STATUS    RESTARTS   AGE
kuryr-pod-1820360092   1/1     Running   0          61m
kuryr-pod-1990564313   1/1     Running   0          90s
kuryr-pod-241193317    1/1     Running   0          95s
kuryr-pod-572786418    1/1     Running   0          61m
(shiftstack) [stack@undercloud-0 ~]$ oc rsh ^C
(shiftstack) [stack@undercloud-0 ~]$ oc get pods -o wide
NAME                   READY   STATUS    RESTARTS   AGE    IP              NODE                          NOMINATED NODE   READINESS GATES
kuryr-pod-1820360092   1/1     Running   0          61m    10.128.47.50    ostest-4b82x-worker-0-q94qc   <none>           <none>
kuryr-pod-1990564313   1/1     Running   0          97s    10.128.46.126   ostest-4b82x-worker-0-q94qc   <none>           <none>
kuryr-pod-241193317    1/1     Running   0          102s   10.128.46.112   ostest-4b82x-worker-0-pk5c9   <none>           <none>
kuryr-pod-572786418    1/1     Running   0          61m    10.128.46.236   ostest-4b82x-worker-0-pk5c9   <none>           <none>
(shiftstack) [stack@undercloud-0 ~]$ oc rsh kuryr-pod-1820360092
~ $ ping 10.128.46.126
PING 10.128.46.126 (10.128.46.126) 56(84) bytes of data.
64 bytes from 10.128.46.126: icmp_seq=1 ttl=64 time=1.21 ms
^C
--- 10.128.46.126 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.210/1.210/1.210/0.000 ms
~ $ exit

Comment 6 errata-xmlrpc 2021-02-24 15:23:22 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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-2020:5633