changing enable-sriov=false does not stop or disable sriov
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
By default sriov is not enabled in this charm, but can easily enabled by running the following command
juju config neutron-openvswitch enable-sriov=true
This will install, and enable sriov as per all the templates, and works as expected. However, when we then use the same command to disable sriov, it doesn't seem to change any configuration. So the command for reference is
juju config neutron-openvswitch enable-sriov=false
Before enabling sriov, there are no files in /etc/ that have sriov in the file, or any files that have sriov in the filename.
After installation and configuration change
The files below have the sriov inside their files
root@juju-
default/
default/
default/
init/neutron-
init/neutron-
init/neutron-
init.d/
init.d/
init.d/
init.d/
init.d/
init.d/
init.d/
neutron/
and the following files have sriov in their name
root@juju-
./systemd/
./systemd/
./systemd/
./rc4.d/
./rc2.d/
./init/
./rc6.d/
./rc3.d/
./rc1.d/
./default/
./rc0.d/
./rc5.d/
./neutron/
./init.
In order to enable SRIOV /ect/default/
--- /etc/default/
+++ /etc/default/
@@ -1,5 +1,5 @@
# Set to 1 to configure Virtual Functions on system startup.
-ENABLE=1
+ENABLE=0
# Blanket configuration for number of Virtual Functions across all NICs
#
# Possible configurations:
Then the service neutron-sriov-agent needs to be disabled and stopped if it's running
For example, if it's been enabled, and then you disable and re-enable, the service for enabling the Neutron SRIOV plugin agent is restarted. There is no indication of the service being stopped when sriov is disabled
Steps to rectify
1. Expect the updated config above config
2. Stop and disable neutron-
3. Stop and disable neutron-sriov-agent service
4. `/usr/local/
Changed in charm-neutron-openvswitch: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Currently the functional tests don't cover the fact that, when the enable-sriov is disabled then the relevant services and the config is changed.
Once this particular is fixed, we ought to update the sriov functional test to test for this