Worked as described in the blog entry:

"The installer will ask if you want to configure your host and cluster for 
Gluster. Again, click "Next" to proceed. In some of my tests, the installer 
failed at this point, with an error message of Failed to execute stage 
'Environment customization'. When I encountered this, I clicked "Restart 
Setup", repeated the above steps, and was able to proceed normally."

https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and-gluster-storage/

After a setup restart this error went away.

The last error i had was in the last stage of the setup process.

The installer was unable to connect to the engine vm after creation and timed 
out after about the 10th retry.
Postinstall failed, but the vm itself was up and running and i was able to ssh 
to it and to connect to the web ui.

Log attached.

Thx Oli

-----Ursprüngliche Nachricht-----
Von: knarra [mailto:kna...@redhat.com] 
Gesendet: Mittwoch, 3. Mai 2017 13:49
An: Oliver Dietzel <o.diet...@rto.de>; 'users@ovirt.org' <users@ovirt.org>
Betreff: Re: AW: [ovirt-users] Ovirt Node 4.1.1.1 installation, engine on 
gluster, existing disk sdb not found or filtered, deployment fails

On 05/03/2017 03:53 PM, Oliver Dietzel wrote:
> Actual size as displayed by lsblk is 558,9G , a combined size of 530 
> GB worked (engine 100, data 180, vmstore 250), but only without thin 
> provisioning. Deployment failed with thin provisioning enabled, but worked 
> with fixed sizes.
>
> Now i hang in hosted engine deployment (having set installation with gluster 
> to yes when asked) with error:
>
> "Failed to execute stage 'Environment customization': Invalid value provided 
> to 'ENABLE_HC_GLUSTER_SERVICE'"
Hi,

     Can you provide me the exact question and your response to that because of 
which your setup failed ?

Thanks
kasturi
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: knarra [mailto:kna...@redhat.com]
> Gesendet: Mittwoch, 3. Mai 2017 12:16
> An: Oliver Dietzel <o.diet...@rto.de>; 'users@ovirt.org' 
> <users@ovirt.org>
> Betreff: Re: [ovirt-users] Ovirt Node 4.1.1.1 installation, engine on 
> gluster, existing disk sdb not found or filtered, deployment fails
>
> On 05/03/2017 03:20 PM, Oliver Dietzel wrote:
>> Thx a lot, i already got rid of the multipaths.
>>
>> Now 5 tries later i try to understand who disk space calc works.
>>
>> I already understand that the combined GByte limit for my drive sdb is 
>> around 530.
>>    
>>> sdb                                                        8:16   0 558,9G  
>>> 0 disk
>> Now the thin pool creation kicks me! :)
>>
>> (i do a  vgremove gluster_vg_sdb on all hosts and reboot all three 
>> hosts between retries)
>>
>> TASK [Create LVs with specified size for the VGs]
>> ******************************
>> failed: [hv1.iw.rto.de] (item={u'lv': u'gluster_thinpool_sdb',
>> u'size': u'530GB', u'extent': u'100%FREE', u'vg': u'gluster_vg_sdb'}) 
>> => {"failed": true, "item": {"extent": "100%FREE", "lv":
>> "gluster_thinpool_sdb", "size": "530GB", "vg": "gluster_vg_sdb"},
>> "msg": "  Insufficient suitable allocatable extents for logical 
>> volume
>> gluster_thinpool_sdb: 135680 more required\n", "rc": 5}
> I think you should input the size as 500GB if your actual disk size is 530 ?
>> -----Ursprüngliche Nachricht-----
>> Von: knarra [mailto:kna...@redhat.com]
>> Gesendet: Mittwoch, 3. Mai 2017 11:17
>> An: Oliver Dietzel <o.diet...@rto.de>; 'users@ovirt.org'
>> <users@ovirt.org>
>> Betreff: Re: [ovirt-users] Ovirt Node 4.1.1.1 installation, engine on 
>> gluster, existing disk sdb not found or filtered, deployment fails
>>
>> On 05/03/2017 02:06 PM, Oliver Dietzel wrote:
>>> Hi,
>>>
>>> i try to set up a 3 node gluster based ovirt cluster, following this guide:
>>> https://www.ovirt.org/blog/2017/04/up-and-running-with-ovirt-4-1-and
>>> -
>>> g
>>> luster-storage/
>>>
>>> oVirt nodes were installed with all disks available in the system, 
>>> installer limited to use only /dev/sda (both sda and sdb are HPE 
>>> logical volumes on a p410 raid controller)
>>>
>>>
>>> Glusterfs deployment fails in the last step before engine setup:
>>>
>>> PLAY RECAP 
>>> *********************************************************************
>>> hv1.iw              : ok=1    changed=1    unreachable=0    failed=0
>>> hv2.iw              : ok=1    changed=1    unreachable=0    failed=0
>>> hv3.iw              : ok=1    changed=1    unreachable=0    failed=0
>>>
>>>
>>> PLAY [gluster_servers]
>>> *********************************************************
>>>
>>> TASK [Clean up filesystem signature]
>>> *******************************************
>>> skipping: [hv1.iw] => (item=/dev/sdb)
>>> skipping: [hv2.iw] => (item=/dev/sdb)
>>> skipping: [hv3.iw] => (item=/dev/sdb)
>>>
>>> TASK [Create Physical Volume]
>>> **************************************************
>>> failed: [hv3.iw] (item=/dev/sdb) => {"failed": true,
>>> "failed_when_result": true, "item": "/dev/sdb", "msg": "  Device 
>>> /dev/sdb not found (or ignored by filtering).\n", "rc": 5}
>>> failed: [hv1.iw] (item=/dev/sdb) => {"failed": true,
>>> "failed_when_result": true, "item": "/dev/sdb", "msg": "  Device 
>>> /dev/sdb not found (or ignored by filtering).\n", "rc": 5}
>>> failed: [hv2.iw] (item=/dev/sdb) => {"failed": true,
>>> "failed_when_result": true, "item": "/dev/sdb", "msg": "  Device 
>>> /dev/sdb not found (or ignored by filtering).\n", "rc": 5}
>>>
>>>
>>> But: /dev/sdb exists on all hosts
>>>
>>> [root@hv1 ~]# lsblk
>>> NAME                                                     MAJ:MIN RM   SIZE 
>>> RO TYPE  MOUNTPOINT
>>> sda                                                        8:0    0 136,7G  
>>> 0 disk
>>> ...
>>> sdb                                                        8:16   0 558,9G  
>>> 0 disk
>>> └─3600508b1001c350a2c1748b0a0ff3860                      253:5    0 558,9G  
>>> 0 mpath
>>>
>>>
>>>
>>> What can i do to make this work?
>>>
>>> ___________________________________________________________
>>> Oliver Dietzel
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>> Hi Oliver,
>>
>>        I see that multipath is enabled on your system and for the device sdb 
>> it creates mpath and once this is created system will identify sdb as 
>> "3600508b1001c350a2c1748b0a0ff3860". To make this work perform the steps 
>> below.
>>
>> 1) multipath -l (to list all multipath devices)
>>
>> 2) black list devices in /etc/multipath.conf by adding the lines below, if 
>> you do not see this file run the command 'vdsm-tool configure --force' which 
>> will create the file for you.
>>
>> blacklist {
>>            devnode "*"
>> }
>>
>> 3) mutipath -F which flushes all the mpath devices.
>>
>> 4) Restart mutipathd by running the command 'systemctl restart multipathd'
>>
>> This should solve the issue.
>>
>> Thanks
>> kasturi.
>>
>> _______________________________________________
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>

--- Begin Message ---
You can now connect to the VM with the following command:
hosted-engine --console
You can also graphically connect to the VM from your system with the following 
command:
remote-viewer vnc://hv1.iw.rto.de:5900
Use temporary password "7393GGzV" to connect to vnc console.
Please ensure that your Guest OS is properly configured to support serial 
console according to your distro documentation.
Follow 
http://www.ovirt.org/Serial_Console_Setup#I_need_to_access_the_console_the_old_way
 for more info.
If you need to reboot the VM you will need to start it manually using the 
command:
hosted-engine --vm-start
You can then set a temporary password using the command:
hosted-engine --add-console-password
|- [ INFO ] Stage: Initializing
|- [ INFO ] Stage: Environment setup
|- Configuration files: 
['/etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf', 
'/etc/ovirt-engine-setup.conf.d/10-packaging.conf', 
'/root/ovirt-engine-answers', '/root/heanswers.conf']
|- Log file: 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20170503124420-tm6vbb.log
|- Version: otopi-1.6.1 (otopi-1.6.1-1.el7.centos)
|- [ INFO ] Stage: Environment packages setup
|- [ INFO ] Stage: Programs detection
|- [ INFO ] Stage: Environment setup
|- [ INFO ] Stage: Environment customization
|-
|- --== PRODUCT OPTIONS ==--
|-
|- Configure Image I/O Proxy on this host? (Yes, No) [Yes]:
|-
|- --== PACKAGES ==--
|-
|-
|- --== NETWORK CONFIGURATION ==--
|-
|- [ INFO ] firewalld will be configured as firewall manager.
|-
|- --== DATABASE CONFIGURATION ==--
|-
|-
|- --== OVIRT ENGINE CONFIGURATION ==--
|-
|-
|- --== STORAGE CONFIGURATION ==--
|-
|-
|- --== PKI CONFIGURATION ==--
|-
|-
|- --== APACHE CONFIGURATION ==--
|-
|-
|- --== SYSTEM CONFIGURATION ==--
|-
|-
|- --== MISC CONFIGURATION ==--
|-
|- Please choose Data Warehouse sampling scale:
|- (1) Basic
|- (2) Full
|- (1, 2)[1]:
|-
|- --== END OF CONFIGURATION ==--
|-
|- [ INFO ] Stage: Setup validation
|- [WARNING] Cannot validate host name settings, reason: resolved host does not 
match any of the local addresses
|-
|- --== CONFIGURATION PREVIEW ==--
|-
|- Application mode : both
|- Default SAN wipe after delete : False
|- Firewall manager : firewalld
|- Update Firewall : True
|- Host FQDN : ovirt-engine.iw.rto.de
|- Configure local Engine database : True
|- Set application as default page : True
|- Configure Apache SSL : True
|- Engine database secured connection : False
|- Engine database user name : engine
|- Engine database name : engine
|- Engine database host : localhost
|- Engine database port : 5432
|- Engine database host name validation : False
|- Engine installation : True
|- PKI organization : iw.rto.de
|- DWH installation : True
|- DWH database secured connection : False
|- DWH database host : localhost
|- DWH database user name : ovirt_engine_history
|- DWH database name : ovirt_engine_history
|- DWH database port : 5432
|- DWH database host name validation : False
|- Configure local DWH database : True
|- Configure Image I/O Proxy : True
|- Configure VMConsole Proxy : True
|- Configure WebSocket Proxy : True
|- [ INFO ] Stage: Transaction setup
|- [ INFO ] Stopping engine service
|- [ INFO ] Stopping ovirt-fence-kdump-listener service
|- [ INFO ] Stopping dwh service
|- [ INFO ] Stopping Image I/O Proxy service
|- [ INFO ] Stopping vmconsole-proxy service
|- [ INFO ] Stopping websocket-proxy service
|- [ INFO ] Stage: Misc configuration
|- [ INFO ] Stage: Package installation
|- [ INFO ] Stage: Misc configuration
|- [ INFO ] Upgrading CA
|- [ INFO ] Initializing PostgreSQL
|- [ INFO ] Creating PostgreSQL 'engine' database
|- [ INFO ] Configuring PostgreSQL
|- [ INFO ] Creating PostgreSQL 'ovirt_engine_history' database
|- [ INFO ] Configuring PostgreSQL
|- [ INFO ] Creating CA
|- [ INFO ] Creating/refreshing Engine database schema
|- [ INFO ] Creating/refreshing DWH database schema
|- [ INFO ] Configuring Image I/O Proxy
|- [ INFO ] Setting up ovirt-vmconsole proxy helper PKI artifacts
|- [ INFO ] Setting up ovirt-vmconsole SSH PKI artifacts
|- [ INFO ] Configuring WebSocket Proxy
|- [ INFO ] Creating/refreshing Engine 'internal' domain database schema
|- [ INFO ] Generating post install configuration file 
'/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'
|- [ INFO ] Stage: Transaction commit
|- [ INFO ] Stage: Closing up
|- [ INFO ] Starting engine service
|- [ INFO ] Starting dwh service
|- [ INFO ] Restarting ovirt-vmconsole proxy service
|-
|- --== SUMMARY ==--
|-
|- [ INFO ] Restarting httpd
|- Please use the user 'admin@internal' and password specified in order to login
|- Web access is enabled at:
|- http://ovirt-engine.iw.rto.de:80/ovirt-engine
|- https://ovirt-engine.iw.rto.de:443/ovirt-engine
|- Internal CA 39:C6:B1:EE:BE:EC:80:93:09:20:6C:22:0A:82:FD:43:65:5D:5DD
|- SSH fingerprint: da:6d:f1:f7:9f:40:b2:a9:32:6c:0a:39:c0:dd:4f:15
|-
|- --== END OF SUMMARY ==--
|-
|- [ INFO ] Stage: Clean up
|- Log file is located at 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20170503124420-tm6vbb.log
|- [ INFO ] Generating answer file 
'/var/lib/ovirt-engine/setup/answers/20170503124836-setup.conf'
|- [ INFO ] Stage: Pre-termination
|- [ INFO ] Stage: Termination
|- [ INFO ] Execution of setup completed successfully
|- HE_APPLIANCE_ENGINE_SETUP_SUCCESS


___________________________________________________________
Oliver Dietzel
Abteilung: Marketing-SEO
RTO GmbH
Hanauer Landstraße 439
60314 Frankfurt

Tel:    +49 69 42085 2222
Fax:    +49 69 42085 400
Email:          o.diet...@rto.de
Web:    www.rto.de





--- End Message ---
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to