Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1655809

Summary:	Director deployed OCP 3.11: openvswitch service is running on the baremetal node by default which doesn't match openshift-ansible defaults
Product:	Red Hat OpenStack	Reporter:	Marius Cornea <mcornea>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin André <m.andre>
Status:	CLOSED ERRATA	QA Contact:	Marius Cornea <mcornea>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	14.0 (Rocky)	CC:	dbecker, gchamoul, ltomasbo, m.andre, mburns, morazi, racedoro
Target Milestone:	rc	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.0.1-0.20181013060904.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:55:06 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 Marius Cornea 2018-12-04 00:47:00 UTC

Description of problem:

Director deployed OCP 3.11: openvswitch service is running on the baremetal node by default[1] when deploying with Director. There are a couple of issues with this:

1/ OCP tested integration matrix[2] states 3.11 was tested agains OVS 2.9 while we ship OVS 2.10 on the overcloud images that get used for the baremetal provisioning

2/ It doesn't follow the openshift-ansible default which run OVS inside containers. 


[1] https://github.com/openstack/tripleo-heat-templates/blob/master/extraconfig/services/openshift-master.yaml#L174
[2] https://access.redhat.com/articles/2176281

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-9.0.1-0.20181013060891.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy OCP overcloud with Director
2. On any of the overcloud node run systemctl status openvswitch

Actual results:
openvswitch service is running on the node

Expected results:
openvswitch service should be disabled and running inside container

Additional info:

Comment 2 Ramon Acedo 2018-12-06 14:43:43 UTC

Linux bridges and Linux bonds will allow every config you can do with OVS bridges/bonds/VLANs. References can be found here:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/advanced_overcloud_customization/#network-interface-reference

If a note in the docs requesting not to use OVS networking for the bare metal nodes is enough I'd suggest doing it that way. If at a technical level we are covered by Linux bridges, as it seems to be the case, you can close this BZ and ensure this is documented. Thanks!

Comment 20 Martin André 2019-01-10 10:12:21 UTC

No doc text required.

Comment 21 errata-xmlrpc 2019-01-11 11:55:06 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, 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/RHEA-2019:0045