+++ This bug was initially created as a clone of Bug #1431108 +++ (cloning for OSP10, from the original bug for OSP 11 ^^^^) Description of problem: As described in the upstream bug at https://bugs.launchpad.net/tripleo/+bug/1669714 wherever openvswitch 2.6 becomes available, any attempt to perform major upgrade or minor update on those nodes is subject to node connectivity problems and ultimately need reboot. We need to remove the special case handling that was previously required when we were going from 2.4 to 2.5.
According to https://bugzilla.redhat.com/show_bug.cgi?id=1424945, the workaround is being added again. Closing this bug.
Update: seems like we should *still* carry a special case upgrade for openvswitch and specifically ovs 2.5.0-14 - I've decided to use the same bug in an attempt to minimize the inevitable confusion here :( Please see the discussion at https://bugzilla.redhat.com/show_bug.cgi?id=1424945#c11 for more information but essentially the workaround is the same as the one we previously had, with the addition of the '--notriggerun' flag for the package update. I have just posted https://review.openstack.org/450607 Add special case upgrade from openvswitch 2.5.0-14 and matbu has this for the ansible steps at https://review.openstack.org/#/c/434346/ moving back to assigned. note that the related patches for removing the workaround had already landed in newton for 11 before this BZ was closed. Adding the new reviews to the trackers (re-adding the workaround with extra flag) even though they aren't against newton (master in review still)
Just cycled back here prompted by an email from Assaf. I was initially told to 'hold' on OSP10 and ovs 2.5 ++ as it wasn't clear what/when it would be available. There are two parts, first we removed the old workaround since it was 'no longer necessary' with https://review.openstack.org/#/c/441192/ and then we re-added it with the --notriggerun flag. This second part we didn't do yet for Newton, so just posted https://review.openstack.org/#/c/458737/ for that and updated trackers, thanks
Please see also BZ#: 1416088. We don't need the latest OVS ROM but we DEFINATELY need something newer. There is some limitation in our AMD CPUs that wwas fixed in a later OVS (2.5.0-22) and all we had to do was pull it from the RHEV channel and make it available in the OSP10 channel and rudate this one RPM only in the images just prior to uploading them to glance.
moving POST https://review.openstack.org/#/c/458737/ just merged to Newton.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1585