Re: [Xen-devel] [xen-unstable test] 25949: regressions - trouble: broken/fail/pass

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 25949: regressions - 
trouble: broken/fail/pass"):
> >>> On 23.04.14 at 03:08, <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> > flight 25949 xen-unstable real [real]
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/25949/ 
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >  test-amd64-i386-xl-qemuu-win7-amd64  5 xen-boot fail REGR. vs. 25945
> 
> The log appears to show that Dom0 booted up fine - were there any
> infrastructure problems (also taking into consideration the broken
> host-install above)?

Actually, the serial log shows a problem.

Firstly, timing.  Unfortunately there is a discrepancy in the
timestamps because the new osstest vm didn't have ntp installed (now
fixed).  I'm going to suffix osstest vm timestamps with [o] and serial
log timestamps with [l].

18:10:41[o] is when osstest timed out waiting for
the system's boot scripts to complete.  It had been waiting since
18:08:59[o], which is when the sshd started accepting connections on
port 22 (all of this is from 5.ts-host-reboot.log).

At 18:10:42[o] osstest sends the first debug keys, requesting serial
input to go to xen (this is from 6.ts-logs-capture.log).  You can see
this in the serial log at 18:10:19[l] (in serial-grain-weevil.log).

In the serial log you can see that the host has in fact not finished
booting by this time.  osstest requests a whole bunch of debug keys
from Xen until 18:11:07[l], at which point it sends a debug key
request that is responded to by the dom0 kernel.  About 11 seconds
later, at 18:11:18[l], the dom0 finally prints its login prompt.

So I think in fact the dom0 kernel was stuck somehow and being prodded
woke it up.  Either that or it was running unconscionably slowly.

A network problem isn't a very good explanation for this failure
because by this point dom0 has been configured to use a static IP
address rather than dhcp.

> >  test-amd64-amd64-xl-qemuu-ovmf-amd64  3 host-install(3) broken REGR. vs. 
> > 25945

This is quite mysterious:

2014-04-22 21:21:43 Z executing ssh ... root@xxxxxxxxxxxxx cat /proc/partitions
2014-04-22 21:21:43 Z | major minor  #blocks  name
2014-04-22 21:21:43 Z | 
2014-04-22 21:21:43 Z |   11        0    1048575 sr0
2014-04-22 21:21:43 Z |    8        0  244140625 sda
2014-04-22 21:21:43 Z |    8       16  244198584 sdb
2014-04-22 21:21:43 Z executing ssh ... root@xxxxxxxxxxxxx pvcreate /dev/sdb
  Device /dev/sdb not found (or ignored by filtering).
2014-04-22 21:21:44 Z command nonzero waitstatus 1280: ssh -o 
StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o 
ServerAliveInterval=100 -o PasswordAuthentication=no -o 
ChallengeResponseAuthentication=no -o 
UserKnownHostsFile=tmp/t.known_hosts_25949.test-amd64-amd64-xl-qemuu-ovmf-amd64 
root@xxxxxxxxxxxxx pvcreate /dev/sdb

Twice in a row.  But it doesn't seem to have been repeated after that.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel