Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have
had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems
(seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch-2.5.0-14.git20160727.el7fdp.x86_64 to openvswitch-2.6.1-8.git20161206.el7fdb.x86_64 testing the N..O upgrade workflow:
Feb 22 12:47:09 overcloud-compute-0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ]
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Started Open vSwitch Database Unit.
Feb 22 12:47:09 overcloud-compute-0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-8.git20161206.el7fdb will be installed
--> Finished Dependency Resolution Updating openvswitch-2.6.1-8.git20161206.el7fdb.x86_64.rpm with nopostun option
... (nothing)
[stack@instack ~]$ ping 192.0.2.16
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https://review.openstack.org/#/c/436990/ Remove the openvswitch special case in tripleo_upgrade_node.sh Icd1517bcade36781fa0da21d045ffd9ec68efc38 (tripleo-heat-templates) to remove this for N..O but iling this bug since we'll need the backports too
Up to openvswitch 2.5 for both minor update and major upgrade in TripleO we have
had to use a special case workaround [1] to upgrade ovs 2.4->2.5 because of
bug 1635205 [2]. This is executed before the general package update as otherwise connectivity would be lost if openvswitch were upgraded with a regular yum update.
However with the arrival of openvswitch 2.6 *using* the workaround causes the
node to lose IPs whilst a regular yum update delivers ovs 2.6 without problems
(seems the rpm script fixes have arrived).
So we need to remove this workaround ... we will need it backported as far as
possible (mitaka presently?). Otherwise wherever openvswitch 2.6 is available
using the workaround to upgrade it will cause the upgrade to hang as the node
loses connectivity:
My local env where I hit this I was going from openvswitch- 2.5.0-14. git20160727. el7fdp. x86_64 to openvswitch- 2.6.1-8. git20161206. el7fdb. x86_64 testing the N..O upgrade workflow:
Feb 22 12:47:09 overcloud- compute- 0.localdomain ovs-ctl[302367]: Configuring Open vSwitch system IDs [ OK ] compute- 0.localdomain systemd[1]: Started Open vSwitch Database Unit. compute- 0.localdomain systemd[1]: Starting Open vSwitch Forwarding Uni 8.git20161206. el7fdb will be installed
Updating openvswitch- 2.6.1-8. git20161206. el7fdb. x86_64. rpm with nopostun option
Feb 22 12:47:09 overcloud-
Feb 22 12:47:09 overcloud-
...
--> Running transaction check
---> Package openvswitch.x86_64 1:2.6.1-
--> Finished Dependency Resolution
... (nothing)
PING 192.0.2.16 (192.0.2.16) 56(84) bytes of data.
From 192.0.2.1 icmp_seq=1 Destination Host Unreachable
I posted https:/ /review. openstack. org/#/c/ 436990/ Remove the openvswitch special case in tripleo_ upgrade_ node.sh Icd1517bcade367 81fa0da21d045ff d9ec68efc38 (tripleo- heat-templates) to remove this for N..O but iling this bug since we'll need the backports too
[1] https:/ /github. com/openstack/ tripleo- heat-templates/ blob/afcb6e01f3 af573a7bdd286a6 5b71eee48cec204 /extraconfig/ tasks/pacemaker _common_ functions. sh#L301- L320 /bugs.launchpad .net/tripleo/ +bug/1635205
[2] https:/