Hide Forgot
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): Newton How reproducible: Everytime Steps to Reproduce: 1. Disable neutron-openvswitch-agent from compute and control profiles in tripleO: resource_registry: OS::TripleO::Services::NeutronOvsAgent: OS::Heat::None OS::TripleO::Services::ComputeNeutronOvsAgent: OS::Heat::None 2. Deploy. 3. Login to a compute node 4. systemctl restart openvswitch Actual results: neutron-openvswitch-agent will also start Expected results: neutron-openvswitch-agent should not start Additional info:
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. Where?
(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. > > Where? Forwarding needinfo to Michal as he's the one who found the patch.
https://github.com/systemd/systemd/commit/c6497ccb7153af9a1252c48918e380b5134314de
fix merged to upstream staging branch -> https://github.com/lnykryn/systemd-rhel/commit/77f4e582d0f381391594e6f8a7b6767d572d96f7 https://github.com/lnykryn/systemd-rhel/commit/7f72b471bbfd449f4261d12cc7b062f6e7034283 -> post
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:2297