Bug 2044503

Summary: [ExternalCloudProvider] installation with additional network on workers fails
Product: OpenShift Container Platform Reporter: Andreas Karis <akaris>
Component: NetworkingAssignee: Andreas Karis <akaris>
Networking sub component: ovn-kubernetes QA Contact: rlobillo
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: medium CC: akaris, anusaxen, itbrown, mifiedle, rlobillo
Version: 4.9   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2035326
: 2059330 (view as bug list) Environment:
Last Closed: 2022-02-10 06:33:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2035326    
Bug Blocks: 2059330    

Comment 5 rlobillo 2022-02-01 13:57:04 UTC 
Verified on OCP4.9.0-0.nightly-2022-01-31-161932 on top of OSP16.1 (RHOS-16.1-RHEL-8-20210903.n.0)

The installation with NetworkType: OVNKubernetes succeeded:

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-01-31-161932   True        False         99m     Cluster version is 4.9.0-0.nightly-2022-01-31-161932
$ cat core_puddle_version 
RHOS-16.1-RHEL-8-20210903.n.0(shiftstack) [stack@undercloud-0 ~]$ oc get pods -n openshift-ovn-kubernetes
NAME                   READY   STATUS    RESTARTS       AGE
ovnkube-master-2x2tv   6/6     Running   0              126m
ovnkube-master-kzbmw   6/6     Running   6 (124m ago)   126m
ovnkube-master-pst98   6/6     Running   6 (125m ago)   126m
ovnkube-node-6hxbj     4/4     Running   1 (110m ago)   111m
ovnkube-node-d4vcl     4/4     Running   1 (123m ago)   126m
ovnkube-node-mftf2     4/4     Running   1 (123m ago)   126m
ovnkube-node-npkdr     4/4     Running   1 (123m ago)   126m
ovnkube-node-whxc9     4/4     Running   1 (110m ago)   111m

On the worker, it is observed below metrics:


$ oc get nodes
NAME                          STATUS   ROLES    AGE    VERSION
ostest-4t2b2-master-0         Ready    master   124m   v1.22.3+2cb6068                                                                                                                       
ostest-4t2b2-master-1         Ready    master   124m   v1.22.3+2cb6068                                                                                                                       
ostest-4t2b2-master-2         Ready    master   124m   v1.22.3+2cb6068                                                                                                                       
ostest-4t2b2-worker-0-dbl6r   Ready    worker   108m   v1.22.3+2cb6068
ostest-4t2b2-worker-0-vrmvq   Ready    worker   108m   v1.22.3+2cb6068                                                                                                                       

$ oc debug node/ostest-4t2b2-worker-0-dbl6r                                                                                                               
Starting pod/ostest-4t2b2-worker-0-dbl6r-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.196.2.113
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4# ip r
default via 10.196.0.1 dev br-ex proto dhcp metric 49
10.128.0.0/14 via 10.131.0.1 dev ovn-k8s-mp0
10.131.0.0/23 dev ovn-k8s-mp0 proto kernel scope link src 10.131.0.2
10.196.0.0/16 dev br-ex proto kernel scope link src 10.196.2.113 metric 49
169.254.169.0/30 via 10.196.0.1 dev br-ex
169.254.169.254 via 10.196.0.10 dev br-ex proto dhcp metric 49
172.30.0.0/16 via 10.196.0.1 dev br-ex mtu 1342
Comment 8 errata-xmlrpc 2022-02-10 06:33: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 (OpenShift Container Platform 4.9.19 bug fix 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/RHBA-2022:0340