Description of problem:
In order to be able to consume the logs from host deploy and engine-setup we need to add timezone to the local timestamp.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Logs include local timestamp without timezone
Logs include local timestamp with timezone
Shirly, you may have different hosts in different time zones for the same deployment. This means that you'll need to convert the time stamp you get.
The right way to handle it is by using UTC for all log files so the system
has a unified sense of time with no need for conversion.
We plan to set the environment in utc. This is for next version.
But in order to consume the logs we MUST have the timestamp with timezone as well and then it can be consumed as UTC automatically.
After more work than most of us expected, the solution chosen for the engine  and vdsm  is to require and use python-dateutil.
otopi must be able to run (in host-deploy flow) on a minimal system, which likely does not have dateutil installed.
I intend to make it not fail if it's missing, but instead run 'date +%z' and use that. Will be a bit ugly.
Copied doc text from bug 1408193 and edited.
Verified in ovirt version 4.2.0-0.0.master.20170827084901.git3fdb878.el7.centos
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.
Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.