Bug 1385096
Summary: | [fdBeta] yum update of openvswitch 2.5 from 2.4 causes restart of openvswitch service that can disrupt network connectivity | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Perry Myers <pmyers> | |
Component: | openvswitch | Assignee: | Flavio Leitner <fleitner> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Rick Alongi <ralongi> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 7.3 | CC: | amuller, atragler, fleitner, kzhang, nyechiel, rkhan | |
Target Milestone: | rc | |||
Target Release: | 7.3 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openvswitch-2.5.0-16.git20160727.el7fdb | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1397045 (view as bug list) | Environment: | ||
Last Closed: | 2017-01-12 17:31:45 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1397045 |
Description
Perry Myers
2016-10-14 18:14:02 UTC
Unfortunately there is no way to guarantee that the network is functional while restarting OVS. For instance, internal ports are TAP devices which are connected to the user-space daemon being restarted. Also that when using DPDK ports, all ports are in user-space and restarting the service means that all DPDK ports will be removed at some point. Having said that, the package will be fixed to not restart the service during the upgrade. The side effect is that security issues won't be applied immediately until a manual service restart or system reboot. There is a catch here that even if we stop restarting the service in the RPM package, upgrading from existing packages will continue to be an issue because the rpm section doing that is %postun.
This is the RPM order during the upgrade:
%pretrans of new package
%pre of new package
(package install)
%post of new package
%triggerin of other packages (set off by installing new package)
%triggerin of new package (if any are true)
%triggerun of old package (if it's set off by uninstalling the old package)
%triggerun of other packages (set off by uninstalling old package)
%preun of old package (removal of old package)
>%postun of old package
%triggerpostun of old package (if it's set off by uninstalling the old package)
%triggerpostun of other packages (if they're setu off by uninstalling the old package)
%posttrans of new package
and I am not finding a way to the new package to prevent the %postun of the old package to be executed.
If you're using rpm directly, then using -U --nopostun would work around the issue.
This is committed on FDBeta and there is no relation with RHEL-7 flags. I'm cloning this one for FDProd to be included in the next batch. The bugfix for this is release already, but due to bz#1403958, there will be at least one more restart during the upgrade. So, I am closing this one as the fix is already there and leave to the other bug to fix any reminder issues. |