[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing



> -----Original Message-----
> From: Ian Campbell [mailto:ian.campbell@xxxxxxxxxx]
> Sent: Monday, October 12, 2015 6:48 PM
> To: Hu, Robert <robert.hu@xxxxxxxxx>; 'Ian Jackson'
> <ian.jackson@xxxxxxxxxxxxx>; 'xen-devel@xxxxxxxxxxxxxxxxxxxx'
> <xen-devel@xxxxxxxxxxxxxxxxxxxx>
> Subject: Re: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing
> 
> On Mon, 2015-10-12 at 10:23 +0000, Hu, Robert wrote:
> 
> (please can you trim your quotes)
> 
> > > Some other issue arises:
> > 1. pax '-M norm', this option isn't support by my RHEL-distributed pax. 
> > Shall
> I
> > simply omit it? or use '-t' substitute it? I tried the latter, seems 
> > working.
> 
> The purpose of "-M norm" is to make the resulting archive deterministic,
> which I don't think -t achieves.
> 
> You can omit it locally I think, but I'd prefer to keep it in git.
> Hopefully newer RHEL will eventually support this.

Yes I will keep it in git. Just change that locally to align with my 
environment.
> 
> 
> > 2. I initially run build-amd64 job, it will firstly re-install host, that's 
> > right. But
> after
> > it is installed, it restarts host and again jump into a manual off-on loop.
> > Do you know which part of code is controlling this?
> 
> The post install check appears to have failed here:
> [...]
> > 2015-10-12 09:59:14 Z executing ssh ... root@xxxxxxxxxxxxxx lvdisplay
> --colon
> >
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @@@@@@@@@@@@@@@@@@@@@@@@
> > @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> >
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @@@@@@@@@@@@@@@@@@@@@@@@
> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> > Someone could be eavesdropping on you right now (man-in-the-middle
> attack)!
> > It is also possible that a host key has just been changed.
> > The fingerprint for the ECDSA key sent by the remote host is
> > 87:a2:7b:8a:73:b4:b4:57:30:15:ee:00:31:df:17:63.
> > Please contact your system administrator.
> > Add correct host key in tmp/t.known_hosts_standalone.build-amd64 to get
> rid of this message.
> > Offending ECDSA key in tmp/t.known_hosts_standalone.build-amd64:1
> > Keyboard-interactive authentication is disabled to avoid man-in-the-middle
> attacks.
> > Permission denied (publickey,password).
> > 2015-10-12 09:59:14 Z command nonzero waitstatus 65280: timeout 60
> 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_standalone.build-amd64
> root@xxxxxxxxxxxxxx lvdisplay --colon
> > status 65280 at Osstest/TestSupport.pm line 410.
> 
> And therefore ts-host-install-twice is trying again, which begins with a
> power off.
> 
> ts-host-install-twice is a workaround for some issues with preseeding LVM
> in Debian installer when there is an existing LVM configuration on the
> host, but it also means that other failures end up having a second go
> (which will probably also fail).
> 
> I think the stuff about known hosts is benign, the "Permission denied
> (publickey,password)." is the real issue, it looks like either ssh cannot
> find your public key or your private key did not correctly get installed on
> the host.
> 
> Looking at patches 10-26 here I don't see anything which I would expect to
> effect host installation in this way. Neither ts-host-install nor
> Osstest/Debian.pm are touched here.
> 
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.