[ovirt-users] Re: "Retrieval of iSCSI targets failed" during hosted engine deployment on oVirt node 4.5

2022-06-20 Thread Guillaume Pavese 
I can confirm that I had exactly the same problem on oVirt 4.4.10
As you said :

"The error suggest that the iSCSI portal port number (which is defaulted to
3260 in the UI) is not being properly passed into the python module
ovirt/ovirt/plugins/modules/ovirt_host.py"


Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group


On Sat, Jun 18, 2022 at 9:47 AM  wrote:

> I was ultimately unable to determine why the GUI is unable to pass the
> port number into the ansible playbooks.
>
> I used the command line installation method instead [*1], and was able to
> successfully complete the hosted engine install w/ iSCSI storage domain
>
> hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true
>
> [*1] -
> https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#Deploying_the_Self-Hosted_Engine_Using_the_CLI_install_RHVM
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7NRKZIBNAOC73CHSELD3M2DAOV7DIR77/
>

-- 


Ce message et toutes les pièces jointes (ci-après le “message”) sont 
établis à l’intention exclusive de ses destinataires et sont confidentiels. 
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir 
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a 
sa destination, toute diffusion ou toute publication, totale ou partielle, 
est interdite, sauf autorisation expresse. L’internet ne permettant pas 
d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) 
décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse 
ou il aurait été modifié. IT, ES, UK.  

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7G7Y55BTVT4AIZZWOHU6UJBGPG4HYFAE/

[ovirt-users] Re: "Retrieval of iSCSI targets failed" during hosted engine deployment on oVirt node 4.5

2022-06-17 Thread pat 
I was ultimately unable to determine why the GUI is unable to pass the port 
number into the ansible playbooks.

I used the command line installation method instead [*1], and was able to 
successfully complete the hosted engine install w/ iSCSI storage domain

hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true

[*1] - 
https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/index.html#Deploying_the_Self-Hosted_Engine_Using_the_CLI_install_RHVM
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7NRKZIBNAOC73CHSELD3M2DAOV7DIR77/

[ovirt-users] Re: Retrieval of iSCSI targets failed.

2019-02-08 Thread Simone Tiraboschi 
On Fri, Feb 8, 2019 at 2:07 AM  wrote:

> Hello!
>
> I was just trying to setup my first oVirt Server via Cockpit but it failed
> when I wanted to connect it to my iSCSI.
>
> These are the last lines of my vdsm.log:
> 2019-02-08 01:34:07,080+0100 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC
> call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312)
>
>
> 2019-02-08 01:34:07,096+0100 INFO  (jsonrpc/5) [api.host] START
> getAllVmIoTunePolicies() from=::1,36420 (api:48)
>
>
> 2019-02-08 01:34:07,096+0100 INFO  (jsonrpc/5) [api.host] FINISH
> getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0},
> 'io_tune_policies_dict': {'be244416-dc4b-4bee-b451-37c0517f19f7':
> {'policy': [], 'current_values': []}}} from=:
> :1,36420 (api:54)
>
>
>
> 2019-02-08 01:34:07,097+0100 INFO  (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC
> call Host.getAllVmIoTunePolicies succeeded in 0.00 seconds (__init__:312)
>
>
> 2019-02-08 01:34:08,149+0100 INFO  (jsonrpc/7) [vdsm.api] START
> discoverSendTargets(con={'ipv6_enabled': u'false', 'connection':
> u'20.20.20.20', 'password': '', 'port': u'3260', 'user': ''}, options=None)
> from=:::192.168.122.144,35682, flow_id=6
> a17a7b3-1dfa-424c-8978-652d73314daf,
> task_id=f8be43e7-9085-42bd-b526-c2adb9962cb4 (api:48)
>
>
> 2019-02-08 01:34:08,330+0100 INFO  (jsonrpc/7) [vdsm.api] FINISH
> discoverSendTargets return={'fullTargets': ['20.20.20.20:3260,1
> iqn.2019-02.eu.teamxenon:data', '20.20.20.20:3260,1
> iqn.2019-02.eu.teamxenon:ovirt'], 'targets': ['iqn.2019-02.eu.teamxe
> non:data', 'iqn.2019-02.eu.teamxenon:ovirt']}
> from=:::192.168.122.144,35682,
> flow_id=6a17a7b3-1dfa-424c-8978-652d73314daf,
> task_id=f8be43e7-9085-42bd-b526-c2adb9962cb4 (api:54)
>
> 2019-02-08 01:34:08,331+0100 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC
> call ISCSIConnection.discoverSendTargets succeeded in 0.18 seconds
> (__init__:312)
>
> 2019-02-08 01:34:10,739+0100 INFO  (vmrecovery) [vdsm.api] START
> getConnectedStoragePoolsList(options=None) from=internal,
> task_id=0507616a-5b31-4d88-897f-0d2411674ce3 (api:48)
>
> 2019-02-08 01:34:10,739+0100 INFO  (vmrecovery) [vdsm.api] FINISH
> getConnectedStoragePoolsList return={'poollist': []} from=internal,
> task_id=0507616a-5b31-4d88-897f-0d2411674ce3 (api:54)
>
> 2019-02-08 01:34:10,740+0100 INFO  (vmrecovery) [vds] recovery: waiting
> for storage pool to go up (clientIF:709)
>
> As you can see it finds the targets but for some reason it fails. The
> initiator name should be configured correctly.
> My iSCSI is configured as the following:
> o- /
> .
> [...]
>
>   o- backstores
> ..
> [...]
>
>   | o- block
> ..
> [Storage Objects: 0]
>
>   | o- fileio
> .
> [Storage Objects: 4]
>
>   | | o- code .
> [/mnt/pool0/vdisks/code.img (200.0GiB) write-back activated]
>
>
>   | | | o- alua
> ...
> [ALUA Groups: 1]
>
>   | | |   o- default_tg_pt_gp
> ...
> [ALUA state: Active/optimized]
>
>   | | o- games ...
> [/mnt/pool1/vdisks/games.img (800.0GiB) write-back activated]
>
>
>   | | | o- alua
> ...
> [ALUA Groups: 1]
>
>   | | |   o- default_tg_pt_gp
> ...
> [ALUA state: Active/optimized]
>
>   | | o- music ...
> [/mnt/pool0/vdisks/music.img (400.0GiB) write-back activated]
>
>
>   | | | o- alua
> ...
> [ALUA Groups: 1]
>
>   | | |   o- default_tg_pt_gp
> ...
> [ALUA state: Active/optimized]
>
>   | | o- virtualization .
> [/mnt/pool0/vdisks/vm.img (100.0GiB) write-back activated]
>
>
>   | |   o- alua
> ...
> [ALUA Groups: 1]
>
>   | | o- default_tg_pt_gp
> ...
> [ALUA state: Active/optimized]
>
>   | o- pscsi
> ..
> [Storage Objects: 0]
>
>   | o- ramdisk
>