Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1598704

Summary: ovirt-system-tests logs and lago logs are on different time zones
Product: [Community] ovirt-system-tests Reporter: Sandro Bonazzola <sbonazzo>
Component: CoreAssignee: Eyal Edri <eedri>
Status: CLOSED UPSTREAM QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.0CC: bugs, gbenhaim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-17 13:14:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: External RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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