openvswitch service is running on the baremetal node by default which doesn't match openshift-ansible defaults

Bug #1807745 reported by Martin André on 2018-12-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Martin André

Bug Description

Originally reported at

openvswitch service is running on the baremetal node by default[1] when deploying with tripleo. 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.


Changed in tripleo:
status: Triaged → In Progress
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers