Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

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

Open
willkelly opened this issue Jun 3, 2014 · 3 comments

Comments

@willkelly
Copy link
Contributor

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
Copy link
Contributor

claco commented Jun 3, 2014

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
Copy link
Contributor Author

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
Copy link
Contributor

claco commented Jun 4, 2014

@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)?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants