[Bug 1586762] Re: Clock skew from host when using adt-virt-qemu runner
brendan.donegan at canonical.com
Mon May 30 14:43:30 UTC 2016
I was assured we were running a recent version but this must not be the
case - thanks for info!
On Mon, 30 May 2016, 14:31 Martin Pitt, <martin.pitt at ubuntu.com> wrote:
> This was fixed almost a year ago in Ubuntu 15.10 (wily) in
> autopkgtest (3.16.3) unstable; urgency=medium
> * Don't invoke QEMU with -localtime. QEMU defaults to and Linux prefers
> hw clock in UTC. This avoids large time jumps when doing NTP.
> -- Martin Pitt <mpitt at debian.org> Thu, 27 Aug 2015 19:54:51 +0200
> So I suggest using the version in trusty-backports or running
> autopkgtest directly from git in your Jenkins instance.
> ** Changed in: autopkgtest (Ubuntu)
> Status: New => Fix Released
> You received this bug notification because you are subscribed to the bug
> Clock skew from host when using adt-virt-qemu runner
> To manage notifications about this bug go to:
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
Clock skew from host when using adt-virt-qemu runner
Status in autopkgtest package in Ubuntu:
We were having issues when trying to collect Junit test results for
MAAS due to the fact that Jenkins was throwing an error saying the
report was too old. We later found that this was because the clock on
the testbed was 3 or so hours behind the host. We noted there is some
code in the adt-virt-qemu runner which attempts to correct the
timezone to the hosts timezone but running this on a qemu instance we
had started ourselves didn't seem to reproduce the issue. After
comparing the qemu-system-x86_64 call made by adt-virt-qemu to one we
had handcrafted ourselves we noted the presence of the '-localtime'
argument in the command used by adt-virt-qemu. Removing this fixed the
At a minimum there needs to be a way to unspecify -localtime so we can
fix the situation in our environment. If the argument is no longer
needed it should be removed wholesale.
To manage notifications about this bug go to:
More information about the foundations-bugs