yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #34631
[Bug 1456760] Re: confusing timestamp related error trace in server log
** 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/1456760
Title:
confusing timestamp related error trace in server log
Status in OpenStack Neutron (virtual network service):
Fix Released
Bug description:
This has been observed in multi-node CI runs for Neutron:
[req-de4ba471-c1d7-49f4-860d-e717c611ebbd None None] Message received
from the host: devstack-trusty-2-node-rax-
iad-2588390-4019.slave.openstack.org during the registration of Open
vSwitch agent has a timestamp: 2015-05-19T18:15:27Z. This differs from
the current server timestamp: 2015-05-19T18:15:27Z by more than the
threshold agent downtime: 75.
What's weird about this is that the two timestamps are the same when
they shouldn't.
This is the logstash query:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZHVyaW5nIHRoZSByZWdpc3RyYXRpb24gb2YgT3BlbiB2U3dpdGNoIGFnZW50IGhhcyBhIHRpbWVzdGFtcFwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiJhbGwiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDMyMDYxMTA1NDUxfQ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1456760/+subscriptions
References