Re: [ovirt-users] hosted-engine cant access engine appliance

[Florian Nolden]

Hello Steffen,

can your nodes resolve the FQDN "ovirtengine.com" to the hosted engine ip (
nslookup ovirtengine.com) ?
If that works have you tried to disable the firewall temporarily?

2016-11-04 14:11 GMT+01:00 Steffen Nolden <
steffen.nol...@alumni.fh-aachen.de>:

> Hello,
>
> i tried to deploy hosted-engine on a testing environment. First of all i
> tried to deploy with the option
>
> "Automatically execute engine-setup on the engine appliance on first
> boot (Yes, No)[Yes]? Yes"
>
> but it got stuck.
>
> [ INFO  ] Running engine-setup on the appliance
> [ ERROR ] Engine setup got stuck on the appliance
> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled on
> the appliance since 600 seconds ago. Please check its log on the appliance.
> [ INFO  ] Stage: Clean up
> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
> setup/answers/answers-20161104112913.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
> please check the issue,fix and redeploy
>   Log file is located at /var/log/ovirt-hosted-engine-s
> etup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log
>
> Next try i said 'No' and i tried to execute it myself. But i can't access
> the engine appliance.
>
> [nolden@oVirtNode01 ~]$ sudo hosted-engine --console
> /usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli uses
> xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli
>from vdsm import utils, vdscli, constants
> The engine VM is running on this host
> Verbunden mit der Domain: HostedEngine
> Escape-Zeichen ist ^]
> Fehler: Interner Fehler: Charakter-Einheit console0 verwendet nicht
> ein PTY
>
> Additionally i can't ping or access the engine appliance via ssh.
>
> Did i forget to install a packege or configure something?
>
> Below my infrastructure and configs. Attached the log file.
>
>
> Thanks for help.
>
>
>
> My infrastructure is a nestedVM system:
> All systems have nested visualization activated
>
> HW with LinuxMint x86_64;
> - VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
> - Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores; Hostname:
> oVirtNode01.com (192.168.122.101): Here i deploy hosted-engine, Hostname:
> oVirtEngine.com (192.168.122.201)
> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
> oVirtNode02.com (192.168.122.102):
> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
> oVirtNode03.com (192.168.122.103):
>
> All three NestedVMs are updated, have installed the ovirt-release40.rpm.
> Additional installed:
> screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
> (4.18.13), bridge-utils (1.5),
> vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.
>
> First NestedVM additional installed ovirt-engine-appliance
> 4.0-20160928.1.el7.centos
>
> The three VMs building a glusterfs volume "engine" 3 replica, with the
> options...
>
> Volume Name: engine
> Type: Replicate
> Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
> Status: Started
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: oVirtNode01.com:/gluster/engine/brick1
> Brick2: oVirtNode02.com:/gluster/engine/brick1
> Brick3: oVirtNode03.com:/gluster/engine/brick1
> Options Reconfigured:
> auth.allow: 192.168.122.*
> storage.owner-gid: 36
> storage.owner-uid: 36
> performance.readdir-ahead: on
>
> ## Session 1 (hosted-engine deploy without automatically execute
> engine-setup)
> [nolden@oVirtNode01 ~]$ sudo hosted-engine --deploy
> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15:
> DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
> deprecated, please use vdsm.jsonrpcvdscli
>   import vdsm.vdscli
> [ INFO  ] Stage: Initializing
> [ INFO  ] Generating a temporary VNC password.
> [ INFO  ] Stage: Environment setup
>   During customization use CTRL-D to abort.
>   Continuing will configure this host for serving as hypervisor
> and create a VM where you have to install the engine afterwards.
>   Are you sure you want to continue? (Yes, No)[Yes]:
> [ INFO  ] Hardware supports virtualization
>   Configuration files: []
>   Log file: /var/log/ovirt-hosted-engine-s
> etup/ovirt-hosted-engine-setup-20161104123834-chwikf.log
>   Version: otopi-1.5.2 (otopi-1.5.2-1.el7.centos)
> [ INFO  ] Stage: Environment packages setup
> [ INFO  ] Stage: Programs detection
> [ INFO  ] Stage: Environment setup
> [ INFO  ] Generating libvirt-spice certificates
> [ INFO  ] Stage: Environment customization
>
>   --== STORAGE CONFIGURATION ==--
>
>   Please specify the storage you would like to use (glusterfs,
> iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
> [ INFO  ] Please note that Replica 3 support is required for the shared
> storage.
>   Please specify the full shared storage connectio

Re: [ovirt-users] hosted-engine cant access engine appliance

[Steffen Nolden]

Hello Florian,

there is no problem to reslove the FQDN

[nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
Server:192.168.122.1
Address:192.168.122.1#53

Name:oVirtEngine.com
Address: 192.168.122.201

The '/etc/hosts' file of each host is configured to resolve the name.

I tried it with stopped firewall,

[nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
[nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; 
vendor preset: enabled)

   Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
  Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid 
$FIREWALLD_ARGS (code=exited, status=0/SUCCESS)

 Main PID: 724 (code=exited, status=0/SUCCESS)

but i got the same error!


Am 04.11.2016 um 15:50 schrieb Florian Nolden:

Hello Steffen,

can your nodes resolve the FQDN "ovirtengine.com 
" to the hosted engine ip ( nslookup 
ovirtengine.com ) ?

If that works have you tried to disable the firewall temporarily?

2016-11-04 14:11 GMT+01:00 Steffen Nolden 
>:


Hello,

i tried to deploy hosted-engine on a testing environment. First of
all i tried to deploy with the option

"Automatically execute engine-setup on the engine appliance on
first boot (Yes, No)[Yes]? Yes"

but it got stuck.

[ INFO  ] Running engine-setup on the appliance
[ ERROR ] Engine setup got stuck on the appliance
[ ERROR ] Failed to execute stage 'Closing up': Engine setup is
stalled on the appliance since 600 seconds ago. Please check its
log on the appliance.
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20161104112913.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system is not
reliable, please check the issue,fix and redeploy
  Log file is located at

/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log

Next try i said 'No' and i tried to execute it myself. But i can't
access the engine appliance.

[nolden@oVirtNode01 ~]$ sudo hosted-engine --console
/usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli
uses xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use
vdsm.jsonrpcvdscli
   from vdsm import utils, vdscli, constants
The engine VM is running on this host
Verbunden mit der Domain: HostedEngine
Escape-Zeichen ist ^]
Fehler: Interner Fehler: Charakter-Einheit console0 verwendet
nicht ein PTY

Additionally i can't ping or access the engine appliance via ssh.

Did i forget to install a packege or configure something?

Below my infrastructure and configs. Attached the log file.


Thanks for help.



My infrastructure is a nestedVM system:
All systems have nested visualization activated

HW with LinuxMint x86_64;
- VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
- Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores;
Hostname: oVirtNode01.com (192.168.122.101): Here i deploy
hosted-engine, Hostname: oVirtEngine.com (192.168.122.201)
- Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores;
Hostname: oVirtNode02.com (192.168.122.102):
- Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores;
Hostname: oVirtNode03.com (192.168.122.103):

All three NestedVMs are updated, have installed the
ovirt-release40.rpm. Additional installed:
screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
(4.18.13), bridge-utils (1.5),
vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.

First NestedVM additional installed ovirt-engine-appliance
4.0-20160928.1.el7.centos

The three VMs building a glusterfs volume "engine" 3 replica, with
the options...

Volume Name: engine
Type: Replicate
Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: oVirtNode01.com:/gluster/engine/brick1
Brick2: oVirtNode02.com:/gluster/engine/brick1
Brick3: oVirtNode03.com:/gluster/engine/brick1
Options Reconfigured:
auth.allow: 192.168.122.*
storage.owner-gid: 36
storage.owner-uid: 36
performance.readdir-ahead: on

## Session 1 (hosted-engine deploy without automatically execute
engine-setup)
[nolden@oVirtNode01 ~]$ sudo hosted-engine --deploy

/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15:
DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
deprecated, please use vdsm.jsonrpcvdscli
  import vdsm.vdscli
[ INFO  ] Stage: Initializing
[ INFO  ] Generating 

Re: [ovirt-users] hosted-engine cant access engine appliance

[Simone Tiraboschi]

On Tue, Nov 8, 2016 at 9:35 AM, Steffen Nolden <
steffen.nol...@alumni.fh-aachen.de> wrote:

> Hello Florian,
>
> there is no problem to reslove the FQDN
>

Can you please attach also VDSM logs fro the relevant time frame?


> [nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
> Server:192.168.122.1
> Address:192.168.122.1#53
>
> Name:oVirtEngine.com
> Address: 192.168.122.201
>
> The '/etc/hosts' file of each host is configured to resolve the name.
>
> I tried it with stopped firewall,
>
> [nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
> [nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
> ● firewalld.service - firewalld - dynamic firewall daemon
>Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
> vendor preset: enabled)
>Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
>   Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid
> $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
>  Main PID: 724 (code=exited, status=0/SUCCESS)
>
> but i got the same error!
>
>
> Am 04.11.2016 um 15:50 schrieb Florian Nolden:
>
> Hello Steffen,
>
> can your nodes resolve the FQDN "ovirtengine.com" to the hosted engine
> ip ( nslookup ovirtengine.com) ?
> If that works have you tried to disable the firewall temporarily?
>
> 2016-11-04 14:11 GMT+01:00 Steffen Nolden  aachen.de>:
>
>> Hello,
>>
>> i tried to deploy hosted-engine on a testing environment. First of all i
>> tried to deploy with the option
>>
>> "Automatically execute engine-setup on the engine appliance on first
>> boot (Yes, No)[Yes]? Yes"
>>
>> but it got stuck.
>>
>> [ INFO  ] Running engine-setup on the appliance
>> [ ERROR ] Engine setup got stuck on the appliance
>> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled
>> on the appliance since 600 seconds ago. Please check its log on the
>> appliance.
>> [ INFO  ] Stage: Clean up
>> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
>> setup/answers/answers-20161104112913.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
>> please check the issue,fix and redeploy
>>   Log file is located at /var/log/ovirt-hosted-engine-s
>> etup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log
>>
>> Next try i said 'No' and i tried to execute it myself. But i can't access
>> the engine appliance.
>>
>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --console
>> /usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli uses
>> xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli
>>from vdsm import utils, vdscli, constants
>> The engine VM is running on this host
>> Verbunden mit der Domain: HostedEngine
>> Escape-Zeichen ist ^]
>> Fehler: Interner Fehler: Charakter-Einheit console0 verwendet nicht
>> ein PTY
>>
>> Additionally i can't ping or access the engine appliance via ssh.
>>
>> Did i forget to install a packege or configure something?
>>
>> Below my infrastructure and configs. Attached the log file.
>>
>>
>> Thanks for help.
>>
>>
>>
>> My infrastructure is a nestedVM system:
>> All systems have nested visualization activated
>>
>> HW with LinuxMint x86_64;
>> - VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
>> - Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores; Hostname:
>> oVirtNode01.com (192.168.122.101): Here i deploy hosted-engine, Hostname:
>> oVirtEngine.com (192.168.122.201)
>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>> oVirtNode02.com (192.168.122.102):
>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>> oVirtNode03.com (192.168.122.103):
>>
>> All three NestedVMs are updated, have installed the ovirt-release40.rpm.
>> Additional installed:
>> screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
>> (4.18.13), bridge-utils (1.5),
>> vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.
>>
>> First NestedVM additional installed ovirt-engine-appliance
>> 4.0-20160928.1.el7.centos
>>
>> The three VMs building a glusterfs volume "engine" 3 replica, with the
>> options...
>>
>> Volume Name: engine
>> Type: Replicate
>> Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
>> Status: Started
>> Number of Bricks: 1 x 3 = 3
>> Transport-type: tcp
>> Bricks:
>> Brick1: oVirtNode01.com:/gluster/engine/brick1
>> Brick2: oVirtNode02.com:/gluster/engine/brick1
>> Brick3: oVirtNode03.com:/gluster/engine/brick1
>> Options Reconfigured:
>> auth.allow: 192.168.122.*
>> storage.owner-gid: 36
>> storage.owner-uid: 36
>> performance.readdir-ahead: on
>>
>> ## Session 1 (hosted-engine deploy without automatically execute
>> engine-setup)
>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --deploy
>> /usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/storage_backends.py:15:
>> DeprecationWarning: vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
>> deprecated, please use vdsm.jsonrp

Re: [ovirt-users] hosted-engine cant access engine appliance

[Simone Tiraboschi]

On Tue, Nov 8, 2016 at 11:30 AM, Steffen Nolden <
steffen.nol...@alumni.fh-aachen.de> wrote:

> Attached the VDSM logs from 'hosted-engine --deploy' to 'hosted-engine
> --console'
>
>
Everything seams fine here.
Now I read that you are using a nested env: do you removed mac spoof
filters on the physical host?


> Am 08.11.2016 um 10:43 schrieb Simone Tiraboschi:
>
>
>
> On Tue, Nov 8, 2016 at 9:35 AM, Steffen Nolden  aachen.de> wrote:
>
>> Hello Florian,
>>
>> there is no problem to reslove the FQDN
>>
>
> Can you please attach also VDSM logs fro the relevant time frame?
>
>
>> [nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
>> Server:192.168.122.1
>> Address:192.168.122.1#53
>>
>> Name:oVirtEngine.com
>> Address: 192.168.122.201
>>
>> The '/etc/hosts' file of each host is configured to resolve the name.
>>
>> I tried it with stopped firewall,
>>
>> [nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
>> [nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
>> ● firewalld.service - firewalld - dynamic firewall daemon
>>Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
>> vendor preset: enabled)
>>Active: inactive (dead) since Di 2016-11-08 09:10:46 CET; 3s ago
>>   Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid
>> $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
>>  Main PID: 724 (code=exited, status=0/SUCCESS)
>>
>> but i got the same error!
>>
>>
>> Am 04.11.2016 um 15:50 schrieb Florian Nolden:
>>
>> Hello Steffen,
>>
>> can your nodes resolve the FQDN "ovirtengine.com" to the hosted engine
>> ip ( nslookup ovirtengine.com) ?
>> If that works have you tried to disable the firewall temporarily?
>>
>> 2016-11-04 14:11 GMT+01:00 Steffen Nolden > en.de>:
>>
>>> Hello,
>>>
>>> i tried to deploy hosted-engine on a testing environment. First of all i
>>> tried to deploy with the option
>>>
>>> "Automatically execute engine-setup on the engine appliance on first
>>> boot (Yes, No)[Yes]? Yes"
>>>
>>> but it got stuck.
>>>
>>> [ INFO  ] Running engine-setup on the appliance
>>> [ ERROR ] Engine setup got stuck on the appliance
>>> [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled
>>> on the appliance since 600 seconds ago. Please check its log on the
>>> appliance.
>>> [ INFO  ] Stage: Clean up
>>> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
>>> setup/answers/answers-20161104112913.conf'
>>> [ INFO  ] Stage: Pre-termination
>>> [ INFO  ] Stage: Termination
>>> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
>>> please check the issue,fix and redeploy
>>>   Log file is located at /var/log/ovirt-hosted-engine-s
>>> etup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log
>>>
>>> Next try i said 'No' and i tried to execute it myself. But i can't
>>> access the engine appliance.
>>>
>>> [nolden@oVirtNode01 ~]$ sudo hosted-engine --console
>>> /usr/share/vdsm/vdsClient.py:33: DeprecationWarning: vdscli uses
>>> xmlrpc. since ovirt 3.6 xmlrpc is deprecated, please use vdsm.jsonrpcvdscli
>>>from vdsm import utils, vdscli, constants
>>> The engine VM is running on this host
>>> Verbunden mit der Domain: HostedEngine
>>> Escape-Zeichen ist ^]
>>> Fehler: Interner Fehler: Charakter-Einheit console0 verwendet nicht
>>> ein PTY
>>>
>>> Additionally i can't ping or access the engine appliance via ssh.
>>>
>>> Did i forget to install a packege or configure something?
>>>
>>> Below my infrastructure and configs. Attached the log file.
>>>
>>>
>>> Thanks for help.
>>>
>>>
>>>
>>> My infrastructure is a nestedVM system:
>>> All systems have nested visualization activated
>>>
>>> HW with LinuxMint x86_64;
>>> - VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
>>> - Nested VM with CentOS-7-x86_64; 12288GB Ram; 4 cores; Hostname:
>>> oVirtNode01.com (192.168.122.101): Here i deploy hosted-engine, Hostname:
>>> oVirtEngine.com (192.168.122.201)
>>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>>> oVirtNode02.com (192.168.122.102):
>>> - Nested VM with CentOS-7-x86_64; 4096GB  Ram; 1 cores; Hostname:
>>> oVirtNode03.com (192.168.122.103):
>>>
>>> All three NestedVMs are updated, have installed the ovirt-release40.rpm.
>>> Additional installed:
>>> screen (4.1.0), ovirt-hosted-engine-setup (2.0.2.2), vdsm-gluster
>>> (4.18.13), bridge-utils (1.5),
>>> vdsm (4.18.13), vdsm-cli (4.18.13), glusterfs-server (3.7.16), samba.
>>>
>>> First NestedVM additional installed ovirt-engine-appliance
>>> 4.0-20160928.1.el7.centos
>>>
>>> The three VMs building a glusterfs volume "engine" 3 replica, with the
>>> options...
>>>
>>> Volume Name: engine
>>> Type: Replicate
>>> Volume ID: e92849b7-af3b-4ccd-bd0d-69a5ab3b6214
>>> Status: Started
>>> Number of Bricks: 1 x 3 = 3
>>> Transport-type: tcp
>>> Bricks:
>>> Brick1: oVirtNode01.com:/gluster/engine/brick1
>>> Brick2: oVirtNode02.com:/gluster/engine/brick1
>>> Brick3: oVirtNode03.com:/gluster/engine/brick1
>

Re: [ovirt-users] hosted-engine cant access engine appliance

[Steffen Nolden]

Am 08.11.2016 um 11:51 schrieb Simone Tiraboschi:



On Tue, Nov 8, 2016 at 11:30 AM, Steffen Nolden 
> wrote:


Attached the VDSM logs from 'hosted-engine --deploy' to
'hosted-engine --console'



Everything seams fine here.
Now I read that you are using a nested env: do you removed mac spoof 
filters on the physical host?


What is it and why is it necessary?
I want to connect from the nested VM to the local engine appliance. And 
that didnt work.

Physical host --> VM --> NestedVM -x-> engine appliance


Am 08.11.2016 um 10:43 schrieb Simone Tiraboschi:



On Tue, Nov 8, 2016 at 9:35 AM, Steffen Nolden
mailto:steffen.nol...@alumni.fh-aachen.de>> wrote:

Hello Florian,

there is no problem to reslove the FQDN


Can you please attach also VDSM logs fro the relevant time frame?

[nolden@oVirtNode01 ~]$ nslookup oVirtEngine.com
Server:192.168.122.1
Address:192.168.122.1#53

Name:oVirtEngine.com
Address: 192.168.122.201

The '/etc/hosts' file of each host is configured to resolve
the name.

I tried it with stopped firewall,

[nolden@oVirtNode01 ~]$ sudo systemctl stop firewalld
[nolden@oVirtNode01 ~]$ sudo systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service;
enabled; vendor preset: enabled)
   Active: inactive (dead) since Di 2016-11-08 09:10:46 CET;
3s ago
  Process: 724 ExecStart=/usr/sbin/firewalld --nofork --nopid
$FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
 Main PID: 724 (code=exited, status=0/SUCCESS)

but i got the same error!


Am 04.11.2016 um 15:50 schrieb Florian Nolden:

Hello Steffen,

can your nodes resolve the FQDN "ovirtengine.com
" to the hosted engine ip ( nslookup
ovirtengine.com ) ?
If that works have you tried to disable the firewall
temporarily?

2016-11-04 14:11 GMT+01:00 Steffen Nolden
mailto:steffen.nol...@alumni.fh-aachen.de>>:

Hello,

i tried to deploy hosted-engine on a testing
environment. First of all i tried to deploy with the option

"Automatically execute engine-setup on the engine
appliance on first boot (Yes, No)[Yes]? Yes"

but it got stuck.

[ INFO  ] Running engine-setup on the appliance
[ ERROR ] Engine setup got stuck on the appliance
[ ERROR ] Failed to execute stage 'Closing up': Engine
setup is stalled on the appliance since 600 seconds ago.
Please check its log on the appliance.
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file

'/var/lib/ovirt-hosted-engine-setup/answers/answers-20161104112913.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system
is not reliable, please check the issue,fix and redeploy
  Log file is located at

/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161104110104-kyhq1e.log

Next try i said 'No' and i tried to execute it myself.
But i can't access the engine appliance.

[nolden@oVirtNode01 ~]$ sudo hosted-engine --console
/usr/share/vdsm/vdsClient.py:33: DeprecationWarning:
vdscli uses xmlrpc. since ovirt 3.6 xmlrpc is
deprecated, please use vdsm.jsonrpcvdscli
   from vdsm import utils, vdscli, constants
The engine VM is running on this host
Verbunden mit der Domain: HostedEngine
Escape-Zeichen ist ^]
Fehler: Interner Fehler: Charakter-Einheit console0
verwendet nicht ein PTY

Additionally i can't ping or access the engine appliance
via ssh.

Did i forget to install a packege or configure something?

Below my infrastructure and configs. Attached the log file.


Thanks for help.



My infrastructure is a nestedVM system:
All systems have nested visualization activated

HW with LinuxMint x86_64;
- VM with CentOS-7-x86_64; 24GB Ram; 7 cores;
- Nested VM with CentOS-7-x86_64; 12288GB Ram; 4
cores; Hostname: oVirtNode01.com (192.168.122.101): Here
i deploy hosted-engine, Hostname: oVirtEngine.com
(192.168.122.201)
- Nested VM with CentOS-7-x86_64; 4096GB Ram; 1
cores; Hostname: oVirtNode02.com (192.168.122.102):
- Nested VM with CentOS-7-x86_64; 4096GB Ram; 1
cores;