Bug 1598704 - ovirt-system-tests logs and lago logs are on different time zones
Summary: ovirt-system-tests logs and lago logs are on different time zones
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: ovirt-system-tests
Classification: Community
Component: Core
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Eyal Edri
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-06 09:10 UTC by Sandro Bonazzola
Modified: 2018-07-17 13:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-17 13:14:57 UTC
oVirt Team: External
Embargoed:


Attachments (Terms of Use)

Description Sandro Bonazzola 2018-07-06 09:10:47 UTC
Trying to correlate logs between lago and VMs, and while in lago logs I see:

2018-07-06 03:38:41,013::log_utils.py::__exit__::611::lago.ssh::DEBUG::end task:c706d3ea-4f3f-4446-9489-1a899a08662d:Get ssh client for lago-he-basic-iscsi-suite-master-host-0:


on one of the host I see:
Jul  5 23:38:41 lago-he-basic-iscsi-suite-master-host-0 systemd-logind: New session 200 of user root.


So the host and lago have 4 hours of difference, making difficult to read the logs.

Comment 2 Eyal Edri 2018-07-08 06:40:15 UTC
Hi,
We stopped using Bugzilla to track OST issues, can you please re-open this in oVirt JIRA? with OST Component?

Example of open tickets:
https://ovirt-jira.atlassian.net/issues/?filter=12824

Comment 3 Sandro Bonazzola 2018-07-17 13:14:57 UTC
Moved upstream to https://ovirt-jira.atlassian.net/browse/OST-110


Note You need to log in before you can comment on or make changes to this bug.