yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => liberty-1

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

Title:
  OVS agent shows connected to AMQP but neutron server rejects the
  request.

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  In my environment, the neutron-server (on the controller) and the
  neutron agent (OVS agent - on the compute host) had a timestamp
  offset.

  The date command shows the following:

  Mon Mar 16 02:50:36 UTC 2015  --> On the compute.
  Mon Mar 16 09:28:52 UTC 2015 --> On the controller.

  The neutron agent in the openvswitch-agent.log says connected to AMQP server on <IP>:5672
  However, the neutron server doesn't seem to register the agent.

  Upon switching on debug - the server.log on the neutron-server shows:

   Message with invalid timestamp received report_state
  /usr/lib/python2.7/site-packages/neutron/db/agents_db.py:232

  There's no way to detect this problem from the compute node - since it
  gives an illusion that the service is connected to AMQP - however,
  only when debugged on the neutron-server, the actual error is
  determined.

  In agents_db.py, report_state should throw back an exception to the
  agent - saying the reporting state failed with the appropriate
  message. This can be achieved by  bubbling an exception from the
  report_state method on a timestamp miss match to the OVS agent.

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