Description of problem: Due to a missing patch in OSP12/Pike networking-ovn will schedule gateways on chassis which could not have external connectivity (which can be discovered by looking at the bridge mappings in the southbound database). This is an issue for compute nodes with no external connectivity, routers will randomly fail. How reproducible: Very likely Steps to Reproduce: 1. setup a multinode deployments, where computes have no bridge-mappings, and have no external connectivity (br-ex typically). 2. create a bunch of routers, and text connectivity. 3. some of them won't respond to pings because it's on an isolated chassis. Actual results: Routers won't ping/work from outside because are isolated Expected results: Routers ping and work because they are scheduled to the right hosts.
Adding release notes entry.
*** Bug 1530191 has been marked as a duplicate of this bug. ***
*** Bug 1530201 has been marked as a duplicate of this bug. ***
fix verified. (overcloud) [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed 12 -p 2018-01-26.2 (overcloud) [root@controller-1 ~]# rpm -qa |grep python-networking-ovn- python-networking-ovn-3.0.0-3.el7ost.noarch After deployment verified that there is not br-ex on compute nodes created a bunch of routers with external connectivity When checked the accessibility to external network it worked. Also, there are no failure on CI that related to this issue.
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:0245