Bug 1510879
| Summary: | OVN deployments shouldn't have bridge-mappings on compute nodes | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Daniel Alvarez Sanchez <dalvarez> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Daniel Alvarez Sanchez <dalvarez> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 12.0 (Pike) | CC: | aschultz, dalvarez, ekuris, jlibosva, jschluet, majopela, mariel, mburns, nusiddiq, qding, rhel-osp-director-maint |
| Target Milestone: | z1 | Keywords: | AutomationBlocker, Triaged, ZStream |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-7.0.3-20.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
All Compute and Controller nodes have bridge-mappings configured, and therefore are eligible to schedule routers. However, if you scheduled a router on a Compute node that doesn't have a connection to an external network, connectivity with the external network fails.
This fix adds the ability to configure bridge-mappings in TripleO and in the director according to roles. This means that you can now exclude Compute nodes from router scheduling and maintain external network connectivity.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-30 21:24:32 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: | |||
| Bug Depends On: | 1525520 | ||
| Bug Blocks: | 1482694 | ||
|
Description
Daniel Alvarez Sanchez
2017-11-08 11:35:35 UTC
Submitted the patch to fix this - https://review.openstack.org/#/c/518440/ and upstream bug link - https://bugs.launchpad.net/tripleo/+bug/1730711 (In reply to Numan Siddique from comment #2) > Submitted the patch to fix this - https://review.openstack.org/#/c/518440/ > and upstream bug link - https://bugs.launchpad.net/tripleo/+bug/1730711 Added those already as external trackers when opened the BZ. Thanks Numan! I think the initial direction to fix this was to setup a DVR-like environment for our OVN jobs. However it'd be better to apply the fix in my opinion since it would be aligned with upstream tripleo environments. Thanks, Daniel *** Bug 1511493 has been marked as a duplicate of this bug. *** Can you please provide the package version where I can find the fix, so I can verify I have the correct package? Hi Eran, the fix is not yet merged [0]. Maybe we can use a mock build? [0] https://code.engineering.redhat.com/gerrit/#/c/123217/ (In reply to Daniel Alvarez Sanchez from comment #6) > Hi Eran, the fix is not yet merged [0]. Maybe we can use a mock build? > [0] https://code.engineering.redhat.com/gerrit/#/c/123217/ Ohh I thought its already merged. So yes when we get a new puddle of OSP12 I will add the fix manually and verify it. (In reply to Daniel Alvarez Sanchez from comment #6) > Hi Eran, the fix is not yet merged [0]. Maybe we can use a mock build? > [0] https://code.engineering.redhat.com/gerrit/#/c/123217/ test it with a mock build and its look ok. (In reply to Daniel Alvarez Sanchez from comment #6) > Hi Eran, the fix is not yet merged [0]. Maybe we can use a mock build? > [0] https://code.engineering.redhat.com/gerrit/#/c/123217/ test it with a mock build and its look ok. Build openstack-tripleo-heat-templates-7.0.3-20.el7ost includes a patch from this bug, please update BZ state accordingly THe bug fix on:
(undercloud) [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed
12 -p 2018-01-16.2
(overcloud) [stack@undercloud-0 ~]$ rpm -qa |grep openstack-tripleo-heat-templates-7.0.
openstack-tripleo-heat-templates-7.0.3-21.el7ost.noarch
[root@controller-0 ~]# ovs-vsctl get open . external_ids
{hostname="controller-0.localdomain", ovn-bridge-mappings="datacentre:br-ex,tenant:br-isolated", ovn-encap-ip="172.17.1.10", ovn-encap-type=geneve, ovn-remote="tcp:172.17.1.20:6642", system-id="bd4321c3-3ef8-40e6-bc19-5d2411da4fd8"}
[root@controller-1 ~]# ovs-vsctl get open . external_ids
{hostname="controller-1.localdomain", ovn-bridge-mappings="datacentre:br-ex,tenant:br-isolated", ovn-encap-ip="172.17.1.17", ovn-encap-type=geneve, ovn-remote="tcp:172.17.1.20:6642", system-id="7cc86fdb-1570-4657-8ceb-e60a726be236"}
[root@controller-2 ~]# ovs-vsctl get open . external_ids
{hostname="controller-2.localdomain", ovn-bridge-mappings="datacentre:br-ex,tenant:br-isolated", ovn-encap-ip="172.17.1.16", ovn-encap-type=geneve, ovn-remote="tcp:172.17.1.20:6642", system-id="2be430af-09c7-4970-8bf9-d8c7eb77e75c"}
[root@compute-0 ~]# ovs-vsctl get open . external_ids
{hostname="compute-0.localdomain", ovn-encap-ip="172.17.1.24", ovn-encap-type=geneve, ovn-remote="tcp:172.17.1.20:6642", system-id="ea8526b8-b8b6-4a00-8dd9-2dbc97bc69b6"}
[root@compute-1 ~]# ovs-vsctl get open . external_ids
{hostname="compute-1.localdomain", ovn-encap-ip="172.17.1.12", ovn-encap-type=geneve, ovn-remote="tcp:172.17.1.20:6642", system-id="5662f345-6ffd-4531-94de-fdb76eb045ff"}
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:0253 |