[Users] ComputeNode installation failed ovirt 3.3

[Fabian Deutsch]

Am Donnerstag, den 10.10.2013, 04:05 -0400 schrieb Alon Bar-Lev:
> 
> ----- Original Message -----
> > From: "Sven Kieske" <S.Kieske at mittwald.de>
> > To: users at ovirt.org
> > Sent: Wednesday, October 9, 2013 12:22:23 PM
> > Subject: [Users] ComputeNode installation failed ovirt 3.3
> > 
> > Hi,
> > 
> > we have successfully deployed ovirt engine 3.3.
> > However, when adding a node based on ovirt node 2.6.1.
> > we get the following error after registration completed successfully
> > and we try to activate the host via webadmin:
> > 
> > "Installing Host server4 Starting vdsm"
> > "Host server4 Installation failed. Unexpected connection termination."
> > 
> > I attached an excerpt from the engine.log, which shows that an ssh
> > commands fails, but I don't know why.
> > 
> > manual ssh connections to the node from the management node work just fine.
> > 
> > The node has the IP 10.0.1.4 in the log.
> 
> You are trying to update not deploy... and you missing the iso image?
> 
> 2013-10-09 10:50:51,423 ERROR [org.ovirt.engine.core.bll.GetoVirtISOsQuery] (ajp--127.0.0.1-8702-11) ovirt ISOs directory not found. Search in: /usr/share/ovirt-node-iso

Hey Alon,

besides this error we also saw this:

 /var/log/ovirt-engine/engine.log:2013-10-10 08:35:27,016 ERROR
[org.ovirt.engine.core.utils.ssh.SSHDialog] (pool-6-thread-4) SSH stderr
during command root at 10.0.1.4:'umask 0077; MYTMP="$(mktemp -t
ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1;
rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; rm -fr "${MYTMP}" && mkdir
"${MYTMP}" && tar --warning=no-timestamp -C "${MYTMP}" -x &&
"${MYTMP}"/setup DIALOG/dialect=str:machine
DIALOG/customization=bool:True': stderr: bash: line 1: 10803
Segmentation fault      "${MYTMP}"/setup DIALOG/dialect=str:machine
DIALOG/customization=bool:True

which shows that there is some segfault.
Is there a way to enable debugging for this bash snippet?
E.g. to keep the MYTMP dir if something goes wrong? Or enable bash -x
(if setup is a bash script) to see what is being called.
To me it's a black box what's happening inside "setup".

Greetings
fabian