[Users] hosted-engine setup fails on RHEL6
Hi, I'm currently trying to setup a hosted-engine on a RHEL6 host with nightly repository (because 3.4 BETA didn't work either): [root@host ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140123135916.log Version: otopi-1.2.0_master (otopi-1.2.0-0.2.master.20140121.git84f0852.el6) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination The full log is available here: http://pastebin.com/Xpa87sjc The matching log entry is below: 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:138 Stage customization METHOD otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._customization 2014-01-23 14:17:48 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND During customization use CTRL-D to abort. 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:630 _check_existing_pools 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 729, in _customization self._check_existing_pools() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request self.send_content(h, request_body) File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content connection.endheaders() File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders self._send_output() File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output self.send(msg) File "/usr/lib64/python2.6/httplib.py", line 739, in send self.connect() File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File "/usr/lib64/python2.6/socket.py", line 567, in create_connection raise error, msg error: [Errno 111] Connection refused 2014-01-23 14:17:48 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused RPM version information: otopi-1.2.0-0.2.master.20140121.git84f0852.el6.noarch ovirt-host-deploy-1.2.0-0.2.master.20140120.gitdeb0453.el6.noarch ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch ovirt-engine-sdk-python-3.4.0.2-1.20140121.git42b7d69.el6.noarch ovirt-release-el6-10.0.1-2.noarch vdsm-python-zombiereaper-4.14.1-6.gite008998.el6.noarch vdsm-python-4.14.1-6.gite008998.el6.x86_64 vdsm-cli-4.14.1-6.gite008998.el6.noarch vdsm-xmlrpc-4.14.1-6.gite008998.el6.noarch vdsm-4.14.1-6.gite008998.el6.x86_64 Any hint? Thanks - Frank
Il 23/01/2014 14:24, Frank Wall ha scritto:
Hi,
I'm currently trying to setup a hosted-engine on a RHEL6 host with nightly repository (because 3.4 BETA didn't work either):
Do you have the same issue you've with nightly?
[root@host ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140123135916.log Version: otopi-1.2.0_master (otopi-1.2.0-0.2.master.20140121.git84f0852.el6) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization
--== STORAGE CONFIGURATION ==--
During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination
The full log is available here: http://pastebin.com/Xpa87sjc
The matching log entry is below:
2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:138 Stage customization METHOD otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._customization 2014-01-23 14:17:48 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:215 DIALOG:SEND During customization use CTRL-D to abort. 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:630 _check_existing_pools 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 729, in _customization self._check_existing_pools() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request self.send_content(h, request_body) File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content connection.endheaders() File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders self._send_output() File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output self.send(msg) File "/usr/lib64/python2.6/httplib.py", line 739, in send self.connect() File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py", line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File "/usr/lib64/python2.6/socket.py", line 567, in create_connection raise error, msg error: [Errno 111] Connection refused 2014-01-23 14:17:48 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused
can you attach vdsm logs?
RPM version information:
otopi-1.2.0-0.2.master.20140121.git84f0852.el6.noarch ovirt-host-deploy-1.2.0-0.2.master.20140120.gitdeb0453.el6.noarch ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch ovirt-engine-sdk-python-3.4.0.2-1.20140121.git42b7d69.el6.noarch ovirt-release-el6-10.0.1-2.noarch vdsm-python-zombiereaper-4.14.1-6.gite008998.el6.noarch vdsm-python-4.14.1-6.gite008998.el6.x86_64 vdsm-cli-4.14.1-6.gite008998.el6.noarch vdsm-xmlrpc-4.14.1-6.gite008998.el6.noarch vdsm-4.14.1-6.gite008998.el6.x86_64
Any hint?
Thanks - Frank _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Hi Sandro, On Thu, Jan 23, 2014 at 02:28:29PM +0100, Sandro Bonazzola wrote:
Do you have the same issue you've with nightly?
on BETA the hosted-engine setup fails (earlier) with another issue that seems to be fixed in NIGHTLY: 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel rhel.status:138 check service vdsmd status 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/initctl', 'status', 'vdsmd'), executable='None', cwd='None', env=None 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/initctl', 'status', 'vdsmd'), rc=1 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stdout: 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stderr: initctl: Unknown job: vdsmd Please don't mixup things... this was the first try on BETA. All other logs are from NIGHTLY :-)
can you attach vdsm logs?
Yes, but only a few lines are logged during hosted-engine setup: MainThread::DEBUG::2014-01-23 14:17:37,132::supervdsmServer::424::SuperVdsm.Server::(main) Terminated normally MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::384::SuperVdsm.Server::(main) Making sure I'm root - SuperVdsm MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::393::SuperVdsm.Server::(main) Parsing cmd args MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::396::SuperVdsm.Server::(main) Cleaning old socket /var/run/vdsm/svdsm.sock MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::400::SuperVdsm.Server::(main) Setting up keep alive thread MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::406::SuperVdsm.Server::(main) Creating remote object manager MainThread::DEBUG::2014-01-23 14:17:37,901::supervdsmServer::417::SuperVdsm.Server::(main) Started serving super vdsm object sourceRoute::DEBUG::2014-01-23 14:17:37,901::sourceRouteThread::56::root::(_subscribeToInotifyLoop) sourceRouteThread.subscribeToInotifyLoop started Thanks - Frank
Il 23/01/2014 14:39, Frank Wall ha scritto:
Hi Sandro,
On Thu, Jan 23, 2014 at 02:28:29PM +0100, Sandro Bonazzola wrote:
Do you have the same issue you've with nightly?
on BETA the hosted-engine setup fails (earlier) with another issue that seems to be fixed in NIGHTLY:
2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel rhel.status:138 check service vdsmd status 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/initctl', 'status', 'vdsmd'), executable='None', cwd='None', env=None 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/initctl', 'status', 'vdsmd'), rc=1 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stdout: 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stderr: initctl: Unknown job: vdsmd
can you attach full logs of this execution?
Please don't mixup things... this was the first try on BETA. All other logs are from NIGHTLY :-)
can you attach vdsm logs?
Yes, but only a few lines are logged during hosted-engine setup:
MainThread::DEBUG::2014-01-23 14:17:37,132::supervdsmServer::424::SuperVdsm.Server::(main) Terminated normally MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::384::SuperVdsm.Server::(main) Making sure I'm root - SuperVdsm MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::393::SuperVdsm.Server::(main) Parsing cmd args MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::396::SuperVdsm.Server::(main) Cleaning old socket /var/run/vdsm/svdsm.sock MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::400::SuperVdsm.Server::(main) Setting up keep alive thread MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::406::SuperVdsm.Server::(main) Creating remote object manager MainThread::DEBUG::2014-01-23 14:17:37,901::supervdsmServer::417::SuperVdsm.Server::(main) Started serving super vdsm object sourceRoute::DEBUG::2014-01-23 14:17:37,901::sourceRouteThread::56::root::(_subscribeToInotifyLoop) sourceRouteThread.subscribeToInotifyLoop started
so vdsmd never started at all?
Thanks - Frank
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Hi Sandro, On Thu, Jan 23, 2014 at 02:43:48PM +0100, Sandro Bonazzola wrote:
on BETA the hosted-engine setup fails (earlier) with another issue that seems to be fixed in NIGHTLY:
2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel rhel.status:138 check service vdsmd status 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:366 execute: ('/sbin/initctl', 'status', 'vdsmd'), executable='None', cwd='None', env=None 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.executeRaw:383 execute-result: ('/sbin/initctl', 'status', 'vdsmd'), rc=1 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:441 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stdout: 2014-01-23 13:50:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:446 execute-output: ('/sbin/initctl', 'status', 'vdsmd') stderr: initctl: Unknown job: vdsmd
can you attach full logs of this execution?
the log from 3.4 BETA test is attached as ovirt-hosted-engine-setup-20140123135527.log.
Please don't mixup things... this was the first try on BETA. All other logs are from NIGHTLY :-)
Yes, but only a few lines are logged during hosted-engine setup:
MainThread::DEBUG::2014-01-23 14:17:37,132::supervdsmServer::424::SuperVdsm.Server::(main) Terminated normally MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,885::netconfpersistence::134::root::(_getConfigs) Non-existing config set. MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::384::SuperVdsm.Server::(main) Making sure I'm root - SuperVdsm MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::393::SuperVdsm.Server::(main) Parsing cmd args MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::396::SuperVdsm.Server::(main) Cleaning old socket /var/run/vdsm/svdsm.sock MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::400::SuperVdsm.Server::(main) Setting up keep alive thread MainThread::DEBUG::2014-01-23 14:17:37,900::supervdsmServer::406::SuperVdsm.Server::(main) Creating remote object manager MainThread::DEBUG::2014-01-23 14:17:37,901::supervdsmServer::417::SuperVdsm.Server::(main) Started serving super vdsm object sourceRoute::DEBUG::2014-01-23 14:17:37,901::sourceRouteThread::56::root::(_subscribeToInotifyLoop) sourceRouteThread.subscribeToInotifyLoop started
so vdsmd never started at all?
Yes, apparently vdsmd doesn't start at all: [root@host ~]# service vdsmd status VDS daemon is not running, and its watchdog is running [root@host ~]# service vdsmd start vdsm: already running [ OK ] vdsm start [ OK ] [root@host ~]# service vdsmd status VDS daemon is not running, and its watchdog is running This results in the supervdsm.log log entries from my previous mail (as seen above). Thanks - Frank
Hi Sandro, This is exactly the same issue I had with BZ 1055153, I recognize all the error messages exactly and the way it occurred. There was also the earlier message on the list which I mentioned my workaround. Thanks, Andrew On Fri, Jan 24, 2014 at 12:28 AM, Sandro Bonazzola <sbonazzo@redhat.com>wrote:
Il 23/01/2014 14:24, Frank Wall ha scritto:
Hi,
I'm currently trying to setup a hosted-engine on a RHEL6 host with nightly repository (because 3.4 BETA didn't work either):
Do you have the same issue you've with nightly?
[root@host ~]# hosted-engine --deploy [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor
and create a VM where you have to install oVirt Engine afterwards.
Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file:
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140123135916.log
Version: otopi-1.2.0_master
[ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization
--== STORAGE CONFIGURATION ==--
During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination
The full log is available here: http://pastebin.com/Xpa87sjc
The matching log entry is below:
2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:138 Stage customization METHOD otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._customization 2014-01-23 14:17:48 DEBUG otopi.plugins.otopi.dialog.human
2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:630 _check_existing_pools 2014-01-23 14:17:48 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-23 14:17:48 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py",
(otopi-1.2.0-0.2.master.20140121.git84f0852.el6) dialog.__logString:215 DIALOG:SEND During customization use CTRL-D to abort. line 729, in _customization
self._check_existing_pools() File
"/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 632, in _check_existing_pools
pools = self.serv.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request self.send_content(h, request_body) File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content connection.endheaders() File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders self._send_output() File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output self.send(msg) File "/usr/lib64/python2.6/httplib.py", line 739, in send self.connect() File "/usr/lib64/python2.6/site-packages/vdsm/SecureXMLRPCServer.py",
line 188, in connect
sock = socket.create_connection((self.host, self.port), self.timeout) File "/usr/lib64/python2.6/socket.py", line 567, in create_connection raise error, msg error: [Errno 111] Connection refused 2014-01-23 14:17:48 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Environment customization': [Errno 111] Connection refused
can you attach vdsm logs?
RPM version information:
otopi-1.2.0-0.2.master.20140121.git84f0852.el6.noarch ovirt-host-deploy-1.2.0-0.2.master.20140120.gitdeb0453.el6.noarch ovirt-hosted-engine-setup-1.2.0-0.0.master.20140117.gitfaf77a5.el6.noarch ovirt-hosted-engine-ha-1.1.0-0.1.beta1.el6.noarch ovirt-engine-sdk-python-3.4.0.2-1.20140121.git42b7d69.el6.noarch ovirt-release-el6-10.0.1-2.noarch vdsm-python-zombiereaper-4.14.1-6.gite008998.el6.noarch vdsm-python-4.14.1-6.gite008998.el6.x86_64 vdsm-cli-4.14.1-6.gite008998.el6.noarch vdsm-xmlrpc-4.14.1-6.gite008998.el6.noarch vdsm-4.14.1-6.gite008998.el6.x86_64
Any hint?
Thanks - Frank _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 01/23/2014 08:24 AM, Frank Wall wrote:
Hi,
I'm currently trying to setup a hosted-engine on a RHEL6 host with nightly repository (because 3.4 BETA didn't work either):
<snip>
[ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination
<snip>
Any hint?
Thanks - Frank
Yep, I get the _same_ exact issue. Please see my e-mail chain from yesterday with the subject line: "oVirt 3.4.0 beta - Hosted Engine Setup -- issues" And look at Andrew Lau's responses who also experienced the same issue ... with a potential work-around which I have yet to try. -Brad
On Thu, Jan 23, 2014 at 09:13:14AM -0500, Brad House wrote:
Yep, I get the _same_ exact issue. Please see my e-mail chain from yesterday with the subject line: "oVirt 3.4.0 beta - Hosted Engine Setup -- issues"
Thanks for the pointer, I guess I missed that :-( As discussed on IRC the issue is related to wrong file permissions and a workaround is described in BZ 1055153 https://bugzilla.redhat.com/show_bug.cgi?id=1055153. Regards - Frank
participants (4)
-
Andrew Lau -
Brad House -
Frank Wall -
Sandro Bonazzola