yahoo-eng-team team mailing list archive

[Matthew Treinish <mtreinish@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1677746

Title:
  neutron-sanity-check always requires ovs to be present

Status in neutron:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1677746/+subscriptions