upgrade-charm hook from neutron-api-plugin-ovn should restart neutron-server service
Bug #2019798 reported by
DUFOUR Olivier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
OpenStack Neutron API OVN Plugin Charm | Status tracked in Trunk | |||||
2023.1 |
New
|
Undecided
|
Unassigned | |||
Trunk |
In Progress
|
Medium
|
Dmytro Kazantsev | |||
Ussuri |
New
|
Undecided
|
Unassigned | |||
Victoria |
New
|
Undecided
|
Unassigned | |||
Wallaby |
New
|
Undecided
|
Unassigned | |||
Xena |
New
|
Undecided
|
Unassigned | |||
Yoga |
New
|
Undecided
|
Unassigned | |||
Zed |
New
|
Undecided
|
Unassigned |
Bug Description
When upgrading the charm, it may modify some configuration files, in particular "/etc/neutron/
While the files are properly generated with the new configuration, the changes are not applied unless neutron-
It would be great to have neutron-
This was discovered when testing a fix for LP#1947391
summary: |
- config-changed hook from neutron-api-plugin-ovn should restart neutron- + upgrade-charm hook from neutron-api-plugin-ovn should restart neutron- server service |
description: | updated |
Changed in charm-neutron-api-plugin-ovn: | |
assignee: | nobody → Dmytro Kazantsev (dkazants) |
To post a comment you must log in.
So the facility does exist in the neutron-api charm for a subordinate to get a restart over the neutron- plugin- api-subordianat es relation using the "restart_trigger" key. However, it doesn't look like the neutron- api-plugin- ovn charm uses the key sadly.
One place to start might be the configure_neutron() function which sets up the data to be sent to the neutron-api principal charm; it would just need to add a 'restart_trigger' using the default str(uuid.uuid4()) assignment to ensure that neutron-api causes a restart.