<div dir="ltr"><div><div>Hi,<br><br></div>It looks like you've been trying to configure the iSCSI bond with a network which was configured as 'required'. This is not allowed by design. Please do the following:<br></div>Navigate to 'Networks' tab, pick the storage network, navigate to the 'Clusters' sub-tab and click on 'Manage Networks' and uncheck the 'Required' check box.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 22, 2016 at 6:27 AM, Budur Nagaraju <span dir="ltr"><<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Yes ,After reboot the Host able to detect the Lun IS , while configuring the iSCSI bond getting the below error.<br><br></div>I have configured a separate network for iSCSI configuration.<br><div><br><br>2016-09-22 08:53:56,603 WARN [org.ovirt.engine.core.bll.<wbr>storage.AddIscsiBondCommand] (ajp--127.0.0.1-8702-11) [24aae7bf] CanDoAction of action AddIscsiBond failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__<wbr>ISCSI_BOND,ACTION_TYPE_FAILED_<wbr>ISCSI_BOND_NETWORK_CANNOT_BE_<wbr>REQUIRED<br>2016-09-22 08:54:16,957 ERROR [org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>SpmStatusVDSCommand] (DefaultQuartzScheduler_<wbr>Worker-64) [58e32f2b] Failed in SpmStatusVDS method<br>2016-09-22 08:54:16,958 ERROR [org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>SpmStatusVDSCommand] (DefaultQuartzScheduler_<wbr>Worker-64) [58e32f2b] Command SpmStatusVDSCommand(HostName = pbuovirt2, HostId = d26d3cb1-df70-472e-964b-<wbr>546ea4dc8bc7, storagePoolId = eb13e6d4-cf50-46e6-a43a-<wbr>234862f1adad) execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to SpmStatusVDS, error = (-202, 'Unable to read resource owners', 'Sanlock exception'), code = 100<br>2016-09-22 08:54:16,960 INFO [org.ovirt.engine.core.bll.<wbr>storage.<wbr>SetStoragePoolStatusCommand] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] Running command: SetStoragePoolStatusCommand internal: true. Entities affected : ID: eb13e6d4-cf50-46e6-a43a-<wbr>234862f1adad Type: StoragePool<br>2016-09-22 08:54:16,962 INFO [org.ovirt.engine.core.<wbr>vdsbroker.storage.<wbr>StoragePoolDomainHelper] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] Storage Pool eb13e6d4-cf50-46e6-a43a-<wbr>234862f1adad - Updating Storage Domain 3511c340-acbb-4c40-aeb2-<wbr>9f4727107a46 status from Active to Unknown, reason : null<br>2016-09-22 08:54:16,968 WARN [org.ovirt.engine.core.dal.<wbr>dbbroker.auditloghandling.<wbr>AuditLogDirector] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] Correlation ID: 79193574, Call Stack: null, Custom Event ID: -1, Message: Invalid status on Data Center EMC. Setting Data Center status to Non Responsive (On host pbuovirt2, Error: General Exception).<br>2016-09-22 08:54:17,355 INFO [org.ovirt.engine.core.<wbr>vdsbroker.<wbr>VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_<wbr>Worker-6) VM child1-leema 29ab1bb4-235d-4b47-ad6a-<wbr>aa7709020327 moved from NotResponding --> Up<br>2016-09-22 08:54:26,992 ERROR [org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>SpmStatusVDSCommand] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] Failed in SpmStatusVDS method<br>2016-09-22 08:54:26,997 ERROR [org.ovirt.engine.core.<wbr>vdsbroker.vdsbroker.<wbr>SpmStatusVDSCommand] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] Command SpmStatusVDSCommand(HostName = pbuovirt2, HostId = d26d3cb1-df70-472e-964b-<wbr>546ea4dc8bc7, storagePoolId = eb13e6d4-cf50-46e6-a43a-<wbr>234862f1adad) execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to SpmStatusVDS, error = (-202, 'Sanlock resource read failure', 'Sanlock exception'), code = 100<br>2016-09-22 08:54:26,997 INFO [org.ovirt.engine.core.<wbr>vdsbroker.irsbroker.<wbr>IrsProxyData] (DefaultQuartzScheduler_<wbr>Worker-64) [79193574] hostFromVds::selectedVds - pbuovirt2, spmStatus returned null!<br>^C<br>[root@pscloud ~]# <br><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 21, 2016 at 6:19 PM, Kevin Goldblatt <span dir="ltr"><<a href="mailto:kgoldbla@redhat.com" target="_blank">kgoldbla@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Badur,<br><br><br><br></div><div>I would like to understand what you are trying to configure.<br><br></div><div>Are you trying to expose a LUN to your vdsm host to use in order to create an ISCSI storage domain?<br></div><div>If so please verify the following:<br><br></div><div>1. Have you correctly mapped the LUN to your vdsm host initiator via your storage provider<br></div><div><br>2. Is the LUN visible via the vdsm host. For this run:<br></div><div>a. "multipath -ll" on the vdsm host. Your output for a LUN should look something like this:<br><br>xxxxxxxxxxxx1600024 dm-6 XxxxxIO ,XxxxxApp <br>size=80G features='0' hwhandler='0' wp=rw<br>`-+- policy='queue-length 0' prio=1 status=active<br> |- 0:0:0:8 sdh 8:112 active ready running<br> |- 0:0:1:8 sdp 8:240 active ready running<br> |- 5:0:0:8 sdx 65:112 active ready running<br> `- 5:0:1:8 sdaf 65:240 active ready running<br><br></div><div>3. Have you edited your /etc/iscsi/initiatorname.iscsi<br></div><div>You should have something like this:<br>InitiatorName=<a href="http://iqn.1xxx-xx.com" target="_blank">iqn.1xxx-xx.com</a>.<wbr>redhat:host1-vds1 (replace the string after the : with the iqn given in the storage provider)<br><br><br></div><div>4. Reboot your host after making any changes<br><br><br></div><div>5. Once you the LUN is visible to the host you can create a Storage Domain via the Ovirt GUI"<br></div><div>a. Select the ISCSI Storage Type<br></div><div>b. Discover the Targets by using one of the IP addresses of the storage provider Ports<br><br></div><div>Hope this helps,<br><br><br><br></div><div>Regards,<br><br><br></div><div>Kevin<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Sep 20, 2016 at 12:54 PM, Budur Nagaraju <span dir="ltr"><<a href="mailto:nbudoor@gmail.com" target="_blank">nbudoor@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div>HI All,<br><br></div>While configuring iSCSI LUN is not getting detected any documents to configure iSCSI in oVirt ?<br><br></div>Thanks,<br></div>Nagaraju<br><br></div>
<br></div></div><span>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>