openvswitch service is running on the baremetal node by default which doesn't match openshift-ansible defaults
Bug #1807745 reported by
Martin André
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
New
|
High
|
Unassigned |
Bug Description
Originally reported at https:/
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.
[1] https:/
[2] https:/
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 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
Changed in tripleo: | |
milestone: | train-2 → train-3 |
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.
This bug has had a related patch abandoned and has been automatically un-assigned due to inactivity. Please re-assign yourself if you are continuing work or adjust the state as appropriate if it is no longer valid.