Description of problem:
When running a tripleo deployment without neutron-openvswitch-agent enabled, if openvswitch is ever restarted, it triggers neutron-openvswitch-agent to start.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Disable neutron-openvswitch-agent from compute and control profiles in tripleO:
3. Login to a compute node
4. systemctl restart openvswitch
neutron-openvswitch-agent will also start
neutron-openvswitch-agent should not start
This is a bug in systemd fixed in upstream. Switching component.
Note that this systemd issue has been affecting OpenStack since the OSP 5 release where we started using systemd on RHEL 7. This is not a regression in OSP 11.
(In reply to Jakub Libosvar from comment #3)
> This is a bug in systemd fixed in upstream.
(In reply to Jan Synacek from comment #6)
> (In reply to Jakub Libosvar from comment #3)
> > This is a bug in systemd fixed in upstream.
Forwarding needinfo to Michal as he's the one who found the patch.
fix merged to upstream staging branch ->
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.