neutron-sanity-check always requires ovs to be present

[Matthew Treinish]

The neutron-sanity-check command has a hard dependency on ovs being present on the system being checked, even if you have all the --noovs* flags set. In my environment I'm running without ovs installed or configured and I hit failures like:

http://paste.openstack.org/show/604926/

even though I ran the command with: --noovsdb_native --noovs_patch --noovs_geneve --noovs_conntrack --noovs_vxlan

From that log it looks like the command is trying to always start the ovs daemon even if all the checks are disabled.

[Brian Haley (brian-haley)]

I can't seem to reproduce this unless I use '--config-file ...' with a filename that has an [ovs] section. Can you give the command-line you ran it with?

[Matthew Treinish (treinish)]

So I was running it with --config-file but there is no [ovs] section in any of the config files I was using.

neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/plugins/ml2/linuxbridge_agent.ini --noovsdb_native --noovs_patch --noovs_geneve --noovs_conntrack --noovs_vxlan

I was able to make it work without setting --config-file at all, but when I specified a --config-file flag, regardless of which file I used it failed like in the paste.

For example I tested it just now with:

neutron-sanity-check --config-file /etc/neutron/plugins/ml2/linuxbridge_agent.ini --noovsdb_native --noovs_patch --noovs_geneve --noovs_conntrack --noovs_vxlan

which only has [linux_bridge], [vxlan], and [securitygroup] sections and it still fails the same way.

[Brian Haley (brian-haley)]

Ok, so using --config-file must cause cfg.CONF to get created, and the default is ovsdb_interface=native, which triggers that check. Someone will have to figure out how to change this since you specified the --no* arguments. Thanks.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.