Avoid upgrading openvswitch along with other packages

Bug #1794833 reported by Brent Eagles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
High
Unassigned

Bug Description

We should exclude openvswitch packages (and possibly os-net-config too?) whenever we do a "yum update" or similar to unintentionally breaking data or control planes.

Tags: tech-debt
Revision history for this message
Cédric Jeanneret (cjeanner) wrote :

Is it still an issue? Isn't ovs in containers now?

Changed in tripleo:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Brent Eagles (beagles) wrote :

Openvswitch is not run in containers yet AFAIK. Even when it is, this bug is still valid because we cannot bounce the openvswitch services without potentially breaking data and control planes.

Please note that the gist of this bug will pretty much remain valid "forever". Regardless of whether openvswitch is running in baremetal or a container, updating it is risky. We probably need to look in an "upgrade this on reboot" mechanism.

tags: added: tech-debt
Changed in tripleo:
importance: Medium → High
Changed in tripleo:
milestone: none → 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
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Incomplete
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
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 report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.