11:03 a.m.
On 12/18/2012 11:21 AM, Neil wrote:
Hi guys,
I'm re-visiting an older issue that I was trying to resolve a while ago.
I have an oVirt 3.1 system that was upgraded from 3.0, during the same
upgrade the hostname of the engine was changed, and the keys etc were
all regenerated.
I'm trying to add a new host to the cluster but my install is failing
with the following error in my "vds_installer.262945.log" ...
Tue, 18 Dec 2012 11:22:26 DEBUG **** Start VDS Installation ****
Tue, 18 Dec 2012 11:22:26 DEBUG get_id_line: read line CentOS
release 6.3 (Final).
Tue, 18 Dec 2012 11:22:26 DEBUG lsb_release: input line CentOS
release 6.3 (Final).
Tue, 18 Dec 2012 11:22:26 DEBUG lsb_release: return: CentOS.
Tue, 18 Dec 2012 11:22:26 DEBUG <BSTRAP component='INSTALLER'
status='OK' message='Test platform succeeded'/>
Tue, 18 Dec 2012 11:22:26 DEBUG trying to fetch deployUtil.py
script cmd = '/usr/bin/curl -s -k -w %{http_code} -o
/tmp/deployUtil.py http://backup.blabl.com/deployUtil.py'
Tue, 18 Dec 2012 11:22:26 DEBUG <BSTRAP component='INSTALLER LIB'
status='FAIL' message='deployUtil.py download failed. Pathname could
not be resolved (verify computer/domain name).'/>
where backup.blabla.com is my oVirt engine.
The host resolves correctly and if I browse to the hostname I receive
the ovirt front end, however if I try and browse to deployUtil.py I
get a 404 error.
Seems like the file either isn't in the correct location on my engine
or the permissions are wrong, below is the file with permissions from
my engine....
-rw-r--r--. 1 root root 46943 Aug 27 16:29
/usr/share/vdsm-bootstrap/deployUtil.py
These are my versions..
ovirt-engine-setup-3.1.0-3.19.el6.noarch
ovirt-engine-3.1.0-3.19.el6.noarch
ovirt-engine-sdk-3.1.0.5-1.el6.noarch
ovirt-engine-jbossas711-1-0.x86_64
ovirt-engine-config-3.1.0-3.19.el6.noarch
ovirt-image-uploader-3.1.0-16.el6.noarch
ovirt-engine-webadmin-portal-3.1.0-3.19.el6.noarch
ovirt-engine-notification-service-3.1.0-3.19.el6.noarch
ovirt-log-collector-3.1.0-16.el6.noarch
ovirt-engine-genericapi-3.1.0-3.19.el6.noarch
ovirt-engine-userportal-3.1.0-3.19.el6.noarch
ovirt-engine-tools-common-3.1.0-3.19.el6.noarch
ovirt-engine-backend-3.1.0-3.19.el6.noarch
ovirt-iso-uploader-3.1.0-16.el6.noarch
ovirt-engine-cli-3.1.0.7-1.el6.noarch
ovirt-engine-restapi-3.1.0-3.19.el6.noarch
ovirt-engine-dbscripts-3.1.0-3.19.el6.noarch
using Centos 6.3 on all hosts and engine
In my engine.log I saw the following in the logs...
<BSTRAP component='INSTALLER LIB' status='OK' message='Install
library
already exists'/>
<BSTRAP component='INSTALLER' status='FAIL'
message='vds_bootstrap.py
download failed. Pathname could not be resolved (verify
computer/domain name).'/>
. FYI. (Stage: Running first installation script on Host)
2012-12-18 12:18:09,360 INFO
[org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper]
(pool-3-thread-47) RunSSHCommand returns true
2012-12-18 12:18:09,360 INFO [org.ovirt.engine.core.bll.VdsInstaller]
(pool-3-thread-47) [63c27417] RunScript ended:true
2012-12-18 12:18:09,361 ERROR [org.ovirt.engine.core.bll.VdsInstaller]
(pool-3-thread-47) [63c27417] Installation of 10.0.2.23. No meaningful
response received from Host. (Stage: Running first installation script
on Host)
I have thoroughly checked hosts, dns and firewalls.
Please shout if any further info is required
Thank you.
Regards.
Neil Wilson.
The URL that the bootstrap should be requesting is this one:
http://backup.blabl.com/Components/vds/deployUtil.py
Can you check that manually with your browser? According to your logs it
is instead requesting this one:
http://backup.blabl.com/deployUtil.py
That won't work, unless you modified the
/usr/share/ovirt-engine/engine.ear/root.war/WEB-INF/web.xml file. You
shouldn't modify it, just check that it contains the following:
<!-- deployUtil.py -->
<servlet>
<servlet-name>deployUtil.py</servlet-name>
<servlet-class>org.ovirt.engine.core.FileServlet</servlet-class>
<init-param>
<param-name>type</param-name>
<param-value>text/plain</param-value>
</init-param>
<init-param>
<param-name>file</param-name>
<param-value>/usr/share/vdsm-bootstrap/deployUtil.py</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>deployUtil.py</servlet-name>
<url-pattern>/Components/vds/deployUtil.py</url-pattern>
</servlet-mapping>
That is how those files are served. You will see something similar for
other .py files required by the bootstrap process. Don't modify this
web.xml file, just check that it is correct.
If you can download the files with your browser but the bootstrap fails
to download them, then there is either a network problem (but you
already checked network and DNS) or the bootstrap proccess is using the
wrong URL. This URL is built using the VdcBootStrapUrl option, stored in
the database. Check its value:
# psql -U engine
Password for user engine: ********
psql (8.4.11)
Type "help" for help.
engine=> select * from vdc_options where option_name = 'VdcBootStrapUrl';
In your system the value should be the following:
http://backup.blabl.com/Components/vds/
If it isn't fix it like this:
# psql -U engine
Password for user engine: ********
psql (8.4.11)
Type "help" for help.
engine=> update vdc_options set option_value =
'http://backup.blabl.com/Components/vds/' where option_name =
'VdcBootStrapUrl';
Then restart the engine and try to install the host again.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.