Bug 2044503 - [ExternalCloudProvider] installation with additional network on workers fails
Summary: [ExternalCloudProvider] installation with additional network on workers fails
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Andreas Karis
QA Contact: rlobillo
Depends On: 2035326
Blocks: 2059330
TreeView+ depends on / blocked
Reported: 2022-01-24 17:32 UTC by Andreas Karis
Modified: 2022-02-28 19:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2035326
: 2059330 (view as bug list)
Last Closed: 2022-02-10 06:33:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2928 0 None open [release-4.9] Bug 2044503: ovs-configuration: use lower than NM default ethernet route metric 2022-01-25 11:46:08 UTC
Red Hat Product Errata RHBA-2022:0340 0 None None None 2022-02-10 06:33:37 UTC

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:
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
sh-4.4# ip r
default via dev br-ex proto dhcp metric 49 via dev ovn-k8s-mp0 dev ovn-k8s-mp0 proto kernel scope link src dev br-ex proto kernel scope link src metric 49 via dev br-ex via dev br-ex proto dhcp metric 49 via 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.


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