Invoking Neutron tasks does not cause Neutron to restart
Bug #1656002 reported by
Dmitry Mescheryakov
This bug report is a duplicate of:
Bug #1613724: Neutron services are not restarted after config changes in common config sections.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
New
|
Undecided
|
Unassigned | ||
Bug Description
Version: 9.2
Steps to reproduce:
1. Install detach-rabbitmq plugin
2. Deploy an environment with 1 controller, 1 compute and 1 rabbitmq node.
3. Add and deploy 1 more rabbitmq node
4. Delete and deploy the change original rabbitmq node (deployed in step #2).
5. Run OSTF tests
The tests will fail because all Neutron services will try to connect to old RabbitMQ, though they will have correct config. The reason is that though the config is changes corresponding tasks are called (see example log http://
| description: | updated |
To post a comment you must log in.
