Change #1098498 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):

[operations/puppet@production] openstack: neutron-openvswitch-agent: prevent puppet from restarting the service

https://gerrit.wikimedia.org/r/1098498

Change #1098498 merged by Arturo Borrero Gonzalez:

[operations/puppet@production] openstack: neutron-openvswitch-agent: prevent puppet from restarting the service

https://gerrit.wikimedia.org/r/1098498

Is there any theory about why restarting openvswitch-agent is more delicate than restarting the old linuxbridge agent?

I'm in favor of avoiding outages, but because the agent runs in many places (cloudvirts), decoupling it from puppet can result in agent state being out of sync with config which also seems bad.

In T380972#10361862, @Andrew wrote:

Is there any theory about why restarting openvswitch-agent is more delicate than restarting the old linuxbridge agent?

I'm in favor of avoiding outages, but because the agent runs in many places (cloudvirts), decoupling it from puppet can result in agent state being out of sync with config which also seems bad.

my current theory is that the linuxbridge agent was stateless, whereas openvswitch is stateful.