[ovirt-users] Cannot retrieve answer file from 1st HE host when setting up 2nd host

[Will Dennis]

Hi Simone,

It's actually OK that it's not fully supported yet, this is a PoC deployment to evaluate oVirt for our needs...

I will provide the VDSM logs shortly & post the URLs.

W.



Sent with Good (www.good.com)


-----Original Message-----
From: Simone Tiraboschi [stirabos at redhat.com<mailto:stirabos at redhat.com>]
Sent: Tuesday, December 22, 2015 03:58 AM Eastern Standard Time
To: Will Dennis; Sahina Bose
Cc: Yedidyah Bar David; users
Subject: Re: [ovirt-users] Cannot retrieve answer file from 1st HE host when setting up 2nd host



On Tue, Dec 22, 2015 at 2:09 AM, Will Dennis <wdennis at nec-labs.com<mailto:wdennis at nec-labs.com>> wrote:
http://ur1.ca/ocstf



2015-12-21 11:28:39 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:219 DIALOG:SEND                 Please specify the full shared storage connection path to use (example: host:/path):
2015-12-21 11:28:55 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:219 DIALOG:RECEIVE    localhost:/engine

OK, so you are trying to deploy hosted-engine on GlusterFS in a hyper-converged way (using the same hosts for virtualization and for serving GlusterFS). Unfortunately I've to advise you that this is not a supported configuration on oVirt 3.6 due to different open bugs.
So I'm glad you can help us testing it but I prefer to advise that today that schema is not production ready.

In your case it seams that VDSM correctly connects the GlusterFS volume seeing all the bricks

2015-12-21 11:28:55 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.nfs plugin.execute:936 execute-output: ('/sbin/gluster', '--mode=script', '--xml', 'volume', 'info', 'engine', '--remote-host=localhost') stdout:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
  <opRet>0</opRet>
  <opErrno>0</opErrno>
  <opErrstr/>
  <volInfo>
    <volumes>
      <volume>
        <name>engine</name>
        <id>974c9da4-b236-4fc1-b26a-645f14601db8</id>
        <status>1</status>
        <statusStr>Started</statusStr>
        <brickCount>6</brickCount>
        <distCount>3</distCount>

but then VDSM doesn't find any storage domain there:

otopi.plugins.ovirt_hosted_engine_setup.storage.storage.Plugin._late_customization
2015-12-21 11:29:58 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._getExistingDomain:476 _getExistingDomain
2015-12-21 11:29:58 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._storageServerConnection:638 connectStorageServer
2015-12-21 11:29:58 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._storageServerConnection:701 {'status': {'message': 'OK', 'code': 0}, 'statuslist': [{'status': 0, 'id': '67ece152-dd66-444c-8d18-4249d1b8f488'}]}
2015-12-21 11:29:58 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._getStorageDomainsList:595 getStorageDomainsList
2015-12-21 11:29:59 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._getStorageDomainsList:598 {'status': {'message': 'OK', 'code': 0}, 'domlist': []}

Can you please attach also the correspondent VDSM logs?

Adding Sahina here.


On Dec 21, 2015, at 11:58 AM, Simone Tiraboschi <stirabos at redhat.com<mailto:stirabos at redhat.com><mailto:stirabos at redhat.com<mailto:stirabos at redhat.com>>> wrote:

On Mon, Dec 21, 2015 at 5:52 PM, Will Dennis <wdennis at nec-labs.com<mailto:wdennis at nec-labs.com><mailto:wdennis at nec-labs.com<mailto:wdennis at nec-labs.com>>> wrote:

However, when I went to the 3rd host and did the setup, I selected 'glusterfs' and gave the path of the engine volume, it came back and incorrectly identified it as the first host, instead of an additional host... How does setup determine that? I confirmed that on this 3rd host that the engine volume is available and has the GUID subfolder of the hosted engine...


Can you please attach a log of hosted-engine-setup also from there?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20151222/112f952f/attachment-0001.html>