[neutron] neutron not restarted appropriately when ovs-neutron-plugin.ini updated

[willkelly]

Hello,

neutron is not restarted when provider network configs are updated resulting in ovs-neutron-plugin.ini changes, so the new provider network is not usable until a manual restart is issued.

https://github.com/rcbops-cookbooks/nova-network/blob/master/recipes/neutron-common.rb#L202-L224

[claco]

Do you have a chef-client run output you can post?

In the code, the change notification for that file is subscribed to by the neutron service for non-https configurations: https://github.com/rcbops-cookbooks/nova-network/blob/3c1cad909cf2589d12756bca6cd518729bc8d41f/recipes/neutron-server.rb#L114

[willkelly]

Unfortunately, I do not, but one can easily reproduce this by setting up a controller, modifying the provider networks, and running chef-client.

You can try to make a neutron network using the new ph-ethX and it will fail. Restart neutron. Rerun your create. It will succeed.

[claco]

@willkelly Can you drop your [sanitized] env json in here to test with? Also, I assume this is the normal run lists (hacontroller1, hacontroller2, single-compute)?