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.
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/ (which I'll also be updating momentarily to point to this bug).