Hi ondra, As you pointed. in your previous mail. The iscsiadm discovered througth 10.11.8.190. It should have probed 10.10.1.1. This may be the root cause. Victor, If you lookup at our playbook. - name: create iscsi_dsk02 ovirt_storage_domains: auth: url: https://rhevm2.res1/ovirt-engine/api token: "{{ ovirt_auth.token }}" insecure: True name: iscsi_dsk02 domain_function: data host: pdx1cr207 data_center: default iscsi: target: iqn.2017-06.stet.iscsi.server:target address: *10.10.1.1* lun_id: 3600140550738b53dd774303bfedac122 state: absent destroy: true register: res_iscsi_dsk02 - debug: var: res_iscsi_dsk02 On Wed, Jun 28, 2017 at 7:58 AM, Ondra Machacek <notifications@github.com> wrote:
It's using the host, which you will pass as host parameter to the task for iscsi discover.
As Yaniv said, can you please share your issue on our mailing list:
users@ovirt.org
There are people with knowledge of iSCSI and they will help you.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/ansible/ansible/issues/25417#issuecomment-311563987>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AScoAyV364pDjqXtCPSNodvhEeLw3b_Sks5sIet0gaJpZM4NyeaB> .