[Users] (no subject)
Hi guys, Shew! Been a busy oVirt week for me :) I'm trying to add a 3rd host into my datacentre but each time the install is failing. In the front end I'm seeing "could not resolve host verify computer/domain name". Below is the log file, with the domain name changed to blabla for privacy reasons 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) return true 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Executing installation stage. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Sending SSH Command chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla ' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,276 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) Invoking chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False on 10.0.2.23 2012-10-19 13:32:11,328 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Received message: <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> <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-10-19 13:32:11,360 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) RunSSHCommand returns true 2012-10-19 13:32:11,361 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] RunScript ended:true 2012-10-19 13:32:11,361 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. No meaningful response received from Host. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-3-thread-50) [14c49c46] After Installation pool-3-thread-50 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] START, SetVdsStatusVDSCommand(vdsId = 67d9a20c-f811-11e1-9004-bb531c164d07, status=InstallFailed, nonOperationalReason=NONE), log id: 50fafc10 2012-10-19 13:32:11,378 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] FINISH, SetVdsStatusVDSCommand, log id: 50fafc10 My engine is engine01.blabla.com My current workings hosts are node01.blabla.com and node02.blabla.com and I'm trying to add node03.blabla.com I can ping node03 as well as the full FQDN node03.blabla.com from the engine as well as the other hosts, there iptables is completely disabled on node03 as well. Node03 has full internet access, it's DNS is working and I can ping all the hosts and engine01.blabla.com etc so I'm fairly certain it's no a networking/DNS issue. A bit of background, I've recently upgraded from an early ovirt 3.1 release, changed the hostname, as well as recreate the SSL certificate on my engine(using Juan's steps). What I do find odd is in the engine log I'm seeing the mention of node02(which is 10.0.2.22), even though I'm specifically trying to install node03(10.0.2.23). I have tried removing the host and re-adding it without any success. On node03 I'm seeing the following error in my /var/log/messages... Oct 19 13:31:32 node03 vdsm root ERROR client ('10.0.2.31', 57654)#012Traceback (most recent call last):#012 File "/usr/lib64/python2.6/SocketServer.py", line 560, in process_request_thread#012 self.finish_request(request, client_address)#012 File "/usr/lib/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 66, in finish_request#012 request.do_handshake()#012 File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake#012 self._sslobj.do_handshake()#012SSLError: [Errno 1] _ssl.c:490: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown Any helps or tips are greatly appreciated. Regards
On 10/19/2012 02:03 PM, Neil wrote:
Hi guys,
Shew! Been a busy oVirt week for me :)
I'm trying to add a 3rd host into my datacentre but each time the install is failing. In the front end I'm seeing "could not resolve host verify computer/domain name". Below is the log file, with the domain name changed to blabla for privacy reasons
2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) return true 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Executing installation stage. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Sending SSH Command chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla ' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,276 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) Invoking chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False on 10.0.2.23 2012-10-19 13:32:11,328 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Received message: <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> <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).'/>
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/ (in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
. FYI. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,360 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) RunSSHCommand returns true 2012-10-19 13:32:11,361 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] RunScript ended:true 2012-10-19 13:32:11,361 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. No meaningful response received from Host. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-3-thread-50) [14c49c46] After Installation pool-3-thread-50 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] START, SetVdsStatusVDSCommand(vdsId = 67d9a20c-f811-11e1-9004-bb531c164d07, status=InstallFailed, nonOperationalReason=NONE), log id: 50fafc10 2012-10-19 13:32:11,378 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] FINISH, SetVdsStatusVDSCommand, log id: 50fafc10
My engine is engine01.blabla.com My current workings hosts are node01.blabla.com and node02.blabla.com and I'm trying to add node03.blabla.com
I can ping node03 as well as the full FQDN node03.blabla.com from the engine as well as the other hosts, there iptables is completely disabled on node03 as well. Node03 has full internet access, it's DNS is working and I can ping all the hosts and engine01.blabla.com etc so I'm fairly certain it's no a networking/DNS issue.
A bit of background, I've recently upgraded from an early ovirt 3.1 release, changed the hostname, as well as recreate the SSL certificate on my engine(using Juan's steps).
What I do find odd is in the engine log I'm seeing the mention of node02(which is 10.0.2.22), even though I'm specifically trying to install node03(10.0.2.23). I have tried removing the host and re-adding it without any success.
On node03 I'm seeing the following error in my /var/log/messages...
Oct 19 13:31:32 node03 vdsm root ERROR client ('10.0.2.31', 57654)#012Traceback (most recent call last):#012 File "/usr/lib64/python2.6/SocketServer.py", line 560, in process_request_thread#012 self.finish_request(request, client_address)#012 File "/usr/lib/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 66, in finish_request#012 request.do_handshake()#012 File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake#012 self._sslobj.do_handshake()#012SSLError: [Errno 1] _ssl.c:490: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown
Any helps or tips are greatly appreciated.
Regards _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Thanks for your assistance Itamar, On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this? Thank you! Neil Wilson.
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thank you!
Neil Wilson.
On Mon, Oct 22, 2012 at 9:16 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thanks Itamar, Yes correct, the db was dumped and re-imported onto the new server. When running engine-config I see that there are two options that still refer to my old engine, I presume both should be changed? engine-config -a | grep -i node VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general VirtualMachineDomainName: node02.blabla.com version: general Also I've tried setting my VdcBootStrapUrl, but I'm battling to get the syntax correct, I've tried all sorts of combinations, but none seem to work, not sure if the key should be quoted, or declared completely or if just the key should be specified etc? [root@backup ~]# engine-config -g VdcBootStrapUrl VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general [root@backup ~]# engine-config -s key=VdcBootStrapUrl backup.blabla.com --cver=http://node02.blabla.com Error setting key's value. No such entry with version http://node02.blabla.com. I've tried specifying the full path, tried quoting and all sorts of different variants of the above combinations without any success. Please could you perhaps give me an example of the correct usage? Thank you. Regards. Neil Wilson.
On 10/22/2012 11:36 AM, Neil wrote:
On Mon, Oct 22, 2012 at 9:16 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thanks Itamar,
Yes correct, the db was dumped and re-imported onto the new server.
When running engine-config I see that there are two options that still refer to my old engine, I presume both should be changed?
engine-config -a | grep -i node VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general VirtualMachineDomainName: node02.blabla.com version: general
Also I've tried setting my VdcBootStrapUrl, but I'm battling to get the syntax correct, I've tried all sorts of combinations, but none seem to work, not sure if the key should be quoted, or declared completely or if just the key should be specified etc?
[root@backup ~]# engine-config -g VdcBootStrapUrl VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general
[root@backup ~]# engine-config -s key=VdcBootStrapUrl backup.blabla.com --cver=http://node02.blabla.com Error setting key's value. No such entry with version http://node02.blabla.com.
cver is the "general" part (or if cluster version specific, 3.0/3.1). just try: engine-config -s VdcBootStrapUrl=http://node02.blabla.com
I've tried specifying the full path, tried quoting and all sorts of different variants of the above combinations without any success. Please could you perhaps give me an example of the correct usage?
Thank you.
Regards.
Neil Wilson.
On Mon, Oct 22, 2012 at 11:59 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 11:36 AM, Neil wrote:
On Mon, Oct 22, 2012 at 9:16 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thanks Itamar,
Yes correct, the db was dumped and re-imported onto the new server.
When running engine-config I see that there are two options that still refer to my old engine, I presume both should be changed?
engine-config -a | grep -i node VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general VirtualMachineDomainName: node02.blabla.com version: general
Also I've tried setting my VdcBootStrapUrl, but I'm battling to get the syntax correct, I've tried all sorts of combinations, but none seem to work, not sure if the key should be quoted, or declared completely or if just the key should be specified etc?
[root@backup ~]# engine-config -g VdcBootStrapUrl VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general
[root@backup ~]# engine-config -s key=VdcBootStrapUrl backup.blabla.com --cver=http://node02.blabla.com Error setting key's value. No such entry with version http://node02.blabla.com.
cver is the "general" part (or if cluster version specific, 3.0/3.1). just try: engine-config -s VdcBootStrapUrl=http://node02.blabla.com
Okay thanks, that worked and allowed me to set it, and I also set the "VirtualMachineDomainName" but I'm still receiving the same error(after restarting ovirt-engine). I've tried to browse to the url you gave me on your first reply both from the new host and one of the existing ones and I receive the following... JBoss Web/7.0.13.Final - Error report HTTP Status 404 - /Components/vds/ type Status report message /Components/vds/ description The requested resource (/Components/vds/) is not available. JBoss Web/7.0.13.Final Seems like something still isn't correct after the upgrade/migration to the new machine... any ideas what to try next? Thanks!
On 10/22/2012 12:26 PM, Neil wrote:
On Mon, Oct 22, 2012 at 11:59 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 11:36 AM, Neil wrote:
On Mon, Oct 22, 2012 at 9:16 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote:
this means the installed host could not download the bootstrap file from the engine. try browsing engine from the host for http://node02.blabla.com:80/Components/vds/
(in 3.2 this is improved by having the engine SCP to node, so this dns resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thanks Itamar,
Yes correct, the db was dumped and re-imported onto the new server.
When running engine-config I see that there are two options that still refer to my old engine, I presume both should be changed?
engine-config -a | grep -i node VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general VirtualMachineDomainName: node02.blabla.com version: general
Also I've tried setting my VdcBootStrapUrl, but I'm battling to get the syntax correct, I've tried all sorts of combinations, but none seem to work, not sure if the key should be quoted, or declared completely or if just the key should be specified etc?
[root@backup ~]# engine-config -g VdcBootStrapUrl VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general
[root@backup ~]# engine-config -s key=VdcBootStrapUrl backup.blabla.com --cver=http://node02.blabla.com Error setting key's value. No such entry with version http://node02.blabla.com.
cver is the "general" part (or if cluster version specific, 3.0/3.1). just try: engine-config -s VdcBootStrapUrl=http://node02.blabla.com
Okay thanks, that worked and allowed me to set it, and I also set the "VirtualMachineDomainName" but I'm still receiving the same error(after restarting ovirt-engine).
I've tried to browse to the url you gave me on your first reply both from the new host and one of the existing ones and I receive the following...
JBoss Web/7.0.13.Final - Error report HTTP Status 404 - /Components/vds/ type Status report message /Components/vds/ description The requested resource (/Components/vds/) is not available. JBoss Web/7.0.13.Final
Seems like something still isn't correct after the upgrade/migration to the new machine... any ideas what to try next?
Thanks!
1. it's case sensitive. 2. did you try running add host again?
Hi Itamar, Apologies for the late reply. 1. it's case sensitive. No problem, I'm only using lowercase 2. did you try running add host again? Yes, completely removed the old host, and tried to re-install it. I'm not sure what to try next. Thank you! Regards. Neil Wilson. On Tue, Oct 23, 2012 at 8:03 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 12:26 PM, Neil wrote:
On Mon, Oct 22, 2012 at 11:59 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 11:36 AM, Neil wrote:
On Mon, Oct 22, 2012 at 9:16 AM, Itamar Heim <iheim@redhat.com> wrote:
On 10/22/2012 09:04 AM, Neil wrote:
Thanks for your assistance Itamar,
On Sun, Oct 21, 2012 at 8:52 AM, Itamar Heim <iheim@redhat.com> wrote: > > > > this means the installed host could not download the bootstrap file > from > the > engine. > try browsing engine from the host for > http://node02.blabla.com:80/Components/vds/ > > (in 3.2 this is improved by having the engine SCP to node, so this > dns > resolution path won't be needed.
So this explains why I'm having the issue then, node02.blabla.com(10.0.2.22) is my old engine, my new engine hostname is backup.blabla.com(10.0.2.23)... any idea how I change this?
did you move the db from one engine to another? use ovirt-config to check all values in the config table which point to the old host and update them (or psql for vdc_options table)
Thanks Itamar,
Yes correct, the db was dumped and re-imported onto the new server.
When running engine-config I see that there are two options that still refer to my old engine, I presume both should be changed?
engine-config -a | grep -i node VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general VirtualMachineDomainName: node02.blabla.com version: general
Also I've tried setting my VdcBootStrapUrl, but I'm battling to get the syntax correct, I've tried all sorts of combinations, but none seem to work, not sure if the key should be quoted, or declared completely or if just the key should be specified etc?
[root@backup ~]# engine-config -g VdcBootStrapUrl VdcBootStrapUrl: http://node02.blabla.com:80/Components/vds/ version: general
[root@backup ~]# engine-config -s key=VdcBootStrapUrl backup.blabla.com --cver=http://node02.blabla.com Error setting key's value. No such entry with version http://node02.blabla.com.
cver is the "general" part (or if cluster version specific, 3.0/3.1). just try: engine-config -s VdcBootStrapUrl=http://node02.blabla.com
Okay thanks, that worked and allowed me to set it, and I also set the "VirtualMachineDomainName" but I'm still receiving the same error(after restarting ovirt-engine).
I've tried to browse to the url you gave me on your first reply both from the new host and one of the existing ones and I receive the following...
JBoss Web/7.0.13.Final - Error report HTTP Status 404 - /Components/vds/ type Status report message /Components/vds/ description The requested resource (/Components/vds/) is not available. JBoss Web/7.0.13.Final
Seems like something still isn't correct after the upgrade/migration to the new machine... any ideas what to try next?
Thanks!
1. it's case sensitive. 2. did you try running add host again?
please attach installation logs from node under /tmp/{vdsm-bootstrap*). also run the following command from your engine machine: psql -U postgres engine -c 'select * from vds_static;' please make sure 'node02.blabla.com' is accessible from host side (first try ping), later try with http request (simply issue wget http://node02.blabla.com:80/Components/vds/vds_bootstrap.py). ----- Original Message -----
From: "Neil" <nwilson123@gmail.com> To: users@ovirt.org Sent: Friday, October 19, 2012 2:03:35 PM Subject: [Users] (no subject)
Hi guys,
Shew! Been a busy oVirt week for me :)
I'm trying to add a 3rd host into my datacentre but each time the install is failing. In the front end I'm seeing "could not resolve host verify computer/domain name". Below is the log file, with the domain name changed to blabla for privacy reasons
2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) return true 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Executing installation stage. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,275 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Sending SSH Command chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla ' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,276 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) Invoking chmod +x /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py; /tmp/vds_installer_52c69f58-90f3-4878-9350-55fa23d5ae53.py -c 'ssl=true;management_port=54321' -O 'blabla' -t 2012-10-19T11:32:10 -p 80 -b http://node02.blabla.com:80/Components/vds/ http://node02.blabla.com:80/Components/vds/ 10.0.2.23 52c69f58-90f3-4878-9350-55fa23d5ae53 False on 10.0.2.23 2012-10-19 13:32:11,328 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. Received message: <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> <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-10-19 13:32:11,360 INFO [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] (pool-3-thread-50) RunSSHCommand returns true 2012-10-19 13:32:11,361 INFO [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] RunScript ended:true 2012-10-19 13:32:11,361 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (pool-3-thread-50) [14c49c46] Installation of 10.0.2.23. No meaningful response received from Host. (Stage: Running first installation script on Host) 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-3-thread-50) [14c49c46] After Installation pool-3-thread-50 2012-10-19 13:32:11,362 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] START, SetVdsStatusVDSCommand(vdsId = 67d9a20c-f811-11e1-9004-bb531c164d07, status=InstallFailed, nonOperationalReason=NONE), log id: 50fafc10 2012-10-19 13:32:11,378 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-3-thread-50) [14c49c46] FINISH, SetVdsStatusVDSCommand, log id: 50fafc10
My engine is engine01.blabla.com My current workings hosts are node01.blabla.com and node02.blabla.com and I'm trying to add node03.blabla.com
I can ping node03 as well as the full FQDN node03.blabla.com from the engine as well as the other hosts, there iptables is completely disabled on node03 as well. Node03 has full internet access, it's DNS is working and I can ping all the hosts and engine01.blabla.com etc so I'm fairly certain it's no a networking/DNS issue.
A bit of background, I've recently upgraded from an early ovirt 3.1 release, changed the hostname, as well as recreate the SSL certificate on my engine(using Juan's steps).
What I do find odd is in the engine log I'm seeing the mention of node02(which is 10.0.2.22), even though I'm specifically trying to install node03(10.0.2.23). I have tried removing the host and re-adding it without any success.
On node03 I'm seeing the following error in my /var/log/messages...
Oct 19 13:31:32 node03 vdsm root ERROR client ('10.0.2.31', 57654)#012Traceback (most recent call last):#012 File "/usr/lib64/python2.6/SocketServer.py", line 560, in process_request_thread#012 self.finish_request(request, client_address)#012 File "/usr/lib/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 66, in finish_request#012 request.do_handshake()#012 File "/usr/lib64/python2.6/ssl.py", line 279, in do_handshake#012 self._sslobj.do_handshake()#012SSLError: [Errno 1] _ssl.c:490: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown
Any helps or tips are greatly appreciated.
Regards _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Haim, On Mon, Oct 22, 2012 at 3:46 PM, Haim Ateya <hateya@redhat.com> wrote:
please attach installation logs from node under /tmp/{vdsm-bootstrap*).
I've checked all of the other logs and they are all the same, so I've only included the latest one... [root@node03 tmp]# cat vds_installer.100915.log Mon, 22 Oct 2012 12:12:04 DEBUG **** Start VDS Installation **** Mon, 22 Oct 2012 12:12:04 DEBUG get_id_line: read line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: input line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: return: CentOS. Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER LIB' status='OK' message='Install library already exists'/> Mon, 22 Oct 2012 12:12:04 DEBUG trying to fetch vds_bootstrap.py script cmd = '/usr/bin/curl -s -k -w %{http_code} -o /tmp/vds_bootstrap_06a0a4ee-8935-4743-8c25-acc13971047b.py http://backup.blabla.com/vds_bootstrap.py' Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='FAIL' message='vds_bootstrap.py download failed. Pathname could not be resolved (verify computer/domain name).'/> [root@node03 tmp]#
also run the following command from your engine machine:
psql -U postgres engine -c 'select * from vds_static;'
Output is attached as output.txt, shows all three hosts along with the correct ip's, node03 has no power management as of yet.
please make sure 'node02.blabla.com' is accessible from host side (first try ping), later try with http request (simply issue wget http://node02.blabla.com:80/Components/vds/vds_bootstrap.py)
Both tests worked fine... node02 is one of my hosts, it used to be my old engine but was changed, backup.blabla.com is my new working engine. [root@node03 ~]# wget http://backup.blabla.com:80/Components/vds/vds_bootstrap.py Connecting to backup.blabla.com|10.0.2.31|:80... connected. HTTP request sent, awaiting response... 200 OK Saving to: âvds_bootstrap.pyâ 2012-10-22 16:08:52 (72.6 MB/s) - âvds_bootstrap.pyâ . Please shout if you need any further info. Thank you! Neil Wilson.
From: "Neil" <nwilson123@gmail.com> To: "Haim Ateya" <hateya@redhat.com> Cc: users@ovirt.org Sent: Monday, October 22, 2012 4:33:11 PM Subject: Re: [Users] (no subject)
Hi Haim,
On Mon, Oct 22, 2012 at 3:46 PM, Haim Ateya <hateya@redhat.com> wrote:
please attach installation logs from node under /tmp/{vdsm-bootstrap*).
I've checked all of the other logs and they are all the same, so I've only included the latest one...
[root@node03 tmp]# cat vds_installer.100915.log Mon, 22 Oct 2012 12:12:04 DEBUG **** Start VDS Installation **** Mon, 22 Oct 2012 12:12:04 DEBUG get_id_line: read line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: input line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: return: CentOS. Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER LIB' status='OK' message='Install library already exists'/> Mon, 22 Oct 2012 12:12:04 DEBUG trying to fetch vds_bootstrap.py script cmd = '/usr/bin/curl -s -k -w %{http_code} -o /tmp/vds_bootstrap_06a0a4ee-8935-4743-8c25-acc13971047b.py http://backup.blabla.com/vds_bootstrap.py' Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='FAIL' message='vds_bootstrap.py download failed. Pathname could not be resolved (verify computer/domain name).'/> [root@node03 tmp]#
also run the following command from your engine machine:
psql -U postgres engine -c 'select * from vds_static;'
Output is attached as output.txt, shows all three hosts along with the correct ip's, node03 has no power management as of yet.
please make sure 'node02.blabla.com' is accessible from host side (first try ping), later try with http request (simply issue wget http://node02.blabla.com:80/Components/vds/vds_bootstrap.py)
Both tests worked fine... node02 is one of my hosts, it used to be my old engine but was changed, backup.blabla.com is my new working engine. so, the problem is that in your engine, VdcBootstrapUrl points to your old engine address (node02.blabla.com:80) instead of your new one (backup.blabla.com), this confuses the host as it tries to download
----- Original Message ----- the script from the old engine, and fails since they are not there. don't really know how you got to this state, but in order to resolve it, please apply the following query: psql -U postgres engine -c "update vdc_options set option_value = 'backup.blabla.com:80/Components/vds/' where option_name = 'VdcBootStrapUrl'"
[root@node03 ~]# wget http://backup.blabla.com:80/Components/vds/vds_bootstrap.py Connecting to backup.blabla.com|10.0.2.31|:80... connected. HTTP request sent, awaiting response... 200 OK Saving to: âvds_bootstrap.pyâ 2012-10-22 16:08:52 (72.6 MB/s) - âvds_bootstrap.pyâ
. Please shout if you need any further info.
Thank you!
Neil Wilson.
----- Original Message -----
From: "Haim Ateya" <hateya@redhat.com> To: "Neil" <nwilson123@gmail.com> Cc: users@ovirt.org Sent: Tuesday, October 23, 2012 12:54:42 PM Subject: Re: [Users] (no subject)
From: "Neil" <nwilson123@gmail.com> To: "Haim Ateya" <hateya@redhat.com> Cc: users@ovirt.org Sent: Monday, October 22, 2012 4:33:11 PM Subject: Re: [Users] (no subject)
Hi Haim,
On Mon, Oct 22, 2012 at 3:46 PM, Haim Ateya <hateya@redhat.com> wrote:
please attach installation logs from node under /tmp/{vdsm-bootstrap*).
I've checked all of the other logs and they are all the same, so I've only included the latest one...
[root@node03 tmp]# cat vds_installer.100915.log Mon, 22 Oct 2012 12:12:04 DEBUG **** Start VDS Installation **** Mon, 22 Oct 2012 12:12:04 DEBUG get_id_line: read line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: input line CentOS release 6.3 (Final). Mon, 22 Oct 2012 12:12:04 DEBUG lsb_release: return: CentOS. Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='OK' message='Test platform succeeded'/> Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER LIB' status='OK' message='Install library already exists'/> Mon, 22 Oct 2012 12:12:04 DEBUG trying to fetch vds_bootstrap.py script cmd = '/usr/bin/curl -s -k -w %{http_code} -o /tmp/vds_bootstrap_06a0a4ee-8935-4743-8c25-acc13971047b.py http://backup.blabla.com/vds_bootstrap.py' Mon, 22 Oct 2012 12:12:04 DEBUG <BSTRAP component='INSTALLER' status='FAIL' message='vds_bootstrap.py download failed. Pathname could not be resolved (verify computer/domain name).'/> [root@node03 tmp]#
also run the following command from your engine machine:
psql -U postgres engine -c 'select * from vds_static;'
Output is attached as output.txt, shows all three hosts along with the correct ip's, node03 has no power management as of yet.
please make sure 'node02.blabla.com' is accessible from host side (first try ping), later try with http request (simply issue wget http://node02.blabla.com:80/Components/vds/vds_bootstrap.py)
Both tests worked fine... node02 is one of my hosts, it used to be my old engine but was changed, backup.blabla.com is my new working engine. so, the problem is that in your engine, VdcBootstrapUrl points to your old engine address (node02.blabla.com:80) instead of your new one (backup.blabla.com), this confuses the host as it tries to download
----- Original Message ----- the script from the old engine, and fails since they are not there. don't really know how you got to this state, but in order to resolve it, please apply the following query:
psql -U postgres engine -c "update vdc_options set option_value = 'backup.blabla.com:80/Components/vds/' where option_name = 'VdcBootStrapUrl'" of-course, with 'http':
psql -U postgres engine -c "update vdc_options set option_value = 'http://backup.blabla.com:80/Components/vds/' where option_name = 'VdcBootStrapUrl'"
[root@node03 ~]# wget http://backup.blabla.com:80/Components/vds/vds_bootstrap.py Connecting to backup.blabla.com|10.0.2.31|:80... connected. HTTP request sent, awaiting response... 200 OK Saving to: âvds_bootstrap.pyâ 2012-10-22 16:08:52 (72.6 MB/s) - âvds_bootstrap.pyâ
. Please shout if you need any further info.
Thank you!
Neil Wilson.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Haim Ateya -
Itamar Heim -
Neil