Newton to Ocata - upgrade to ovs 2.5->2.6 with current workaround and lose connectivity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Marios Andreou |
Bug Description
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-
Feb 22 12:47:09 overcloud-
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
Updating openvswitch-
... (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:/
[1] https:/
[2] https:/
description: | updated |
description: | updated |
Changed in tripleo: | |
milestone: | pike-1 → ocata-rc2 |
tags: | added: ocata-backport-potential |
tags: | added: mitaka-backport-potential newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-rc2 → pike-1 |
Changed in tripleo: | |
milestone: | pike-1 → ongoing |
Fix proposed to branch: stable/ocata /review. openstack. org/441184
Review: https:/