Comment # 20 on bug 1117483 from Jaime Caama�o Ruiz

(In reply to Franck Bui from comment #19)

> Could you give me the status of openvswitch ?
> 
> Does it still use DISABLE_RESTART_ON_UPDATE ? if so why exactly and how a
> sysadmin is supposed to use it ? by globally disable the restart of all
> packages ?

We use DISABLE_RESTART_ON_UPDATE=yes on spec %postun section before using the
%service_del_postun macro. This is not a global use of
DISABLE_RESTART_ON_UPDATE and only affects services handled in openvswitch
package. sysadmin is not expected to do anything other than restarting the
affected upgraded services at his convenience. The affected services handled in
the openvswitch package are:

ovsdb-server.service
ovs-vswitchd.service
openvswitch.service
ovn-northd.service
ovn-controller.service
ovn-controller-vtep.service
openvswitch-testcontroller.service

For the first three listed services, the purpose of preventing the restart is
to avoid inadvertent loss of information that could happen upon restart. This
is aligned to the upstream approach. I am unsure about the other services, but
probably the use of DISABLE_RESTART_ON_UPDATE could be dropped for those.

>Well as maintainer of systemd-rpm-macros and for the reasons given above, we >want to get rid of DISABLE_RESTART_ON_UPDATE.

We can stop using DISABLE_RESTART_ON_UPDATE. We can use '%service_del_postun
-n' instead. Is that OK?