[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  Xen ovs-agent-plugin polling manager is reported as not active

Status in neutron:

Bug description:
  My environment is XenServer + Neutron with ML2 plugin, OVS as driver, VLan 
  This is a single box environment installed by devstack.
  When it began to run, I found q-agt always had error logs like this:

  2015-09-09 05:15:23.653 ERROR neutron.agent.linux.ovsdb_monitor [req-
  2dfc6939-277b-4d54-83d5-d0aecbfdc07c None None] Interface monitor is
  not active

  Dig deep into the code, I found the callstack is trace from
  OVSNeutronAgent.rpc_loop() to neutron/agent/linux/utils.py
  remove_abs_path(). So I temporarily added debug log and found

  2015-09-09 05:15:23.653 DEBUG neutron.agent.linux.utils 
[req-2dfc6939-277b-4d54-83d5-d0aecbfdc07c None None] cmd_matches_expected, 
cmd:['/usr/bin/python', '/usr/local/bin/neutron-rootwrap-xen-dom0', 
'/etc/neutron/rootwrap.conf', 'ovsdb-client', 'monitor', 'Interface', 
'name,ofport,external_ids', '--format=json'], expect:['ovsdb-client', 
'monitor', 'Interface', 'name,ofport,external_ids', '--format=json'] from 
(pid=11595) cmd_matches_expected 
  So, it's clear that after remove absolute path, the command still cannot 
match, so it will lead to the ERROR log of "Interface monitor is not active"

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to