Neutron service was not restarted after executing openstack config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Bartosz Kupidura | ||
8.0.x |
Fix Released
|
High
|
Bartosz Kupidura |
Bug Description
ISO: 466
Test: Reconfigure neutron ml2 VLAN range
Scenario:
1. Revert snapshot "basic_
2. Upload a new openstack configuration for neutron with new network_vlan_ranges [1]
3. Get uptime of process "neutron-server" on each controller
4. Apply a new VLAN range(minimal range) to all nodes
5. Wait for configuration applying
6. Check that service "neutron-server" was restarted
7. Verify ml2 plugin settings
8. Create new private network
9. Try to create one more, verify that it is impossible
Test fail on step 6, "neutron-server" was not restarted
[1] http://
[2] Failed swarm: https:/
After investigation it was found that after we repeat the execute one the same env with the same config it would be applied and services will be restarted.
In puppet log for for the test case you can see that service wasn't restart:
[3] http://
And this is how the log looks like if new configurations are applied:
Changed in fuel: | |
status: | New → Confirmed |
summary: |
- Neutron service was not restarted after applying openstack config + Neutron service was not restarted after executing openstack config |
description: | updated |
Changed in fuel: | |
assignee: | Fuel QA telco (fuel-qa-telco) → Fuel Mixed (fuel-mixed-team) |
tags: |
added: area-library removed: area-qa |
tags: | added: regression-8.0 |
tags: | added: feature |
tags: |
added: feature-openstack-config-change removed: feature |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Changed in fuel: | |
assignee: | Fuel QA telco (fuel-qa-telco) → Sergey Novikov (snovikov) |
tags: | added: team-telco |
tags: |
added: area-qa removed: area-library |
tags: |
added: area-library removed: area-qa |
Looks like: default_ quota is already missing from file
DEFAULT/debug already has already value True
quotas/
So there is no need for restart.