8:19 a.m.
Hi,
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:
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.
On Thu, Sep 22, 2016 at 6:27 AM, Budur Nagaraju <nbudoor(a)gmail.com> wrote:
Yes ,After reboot the Host able to detect the Lun IS , while
configuring
the iSCSI bond getting the below error.
I have configured a separate network for iSCSI configuration.
2016-09-22 08:53:56,603 WARN [org.ovirt.engine.core.bll.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__
ISCSI_BOND,ACTION_TYPE_FAILED_ISCSI_BOND_NETWORK_CANNOT_BE_REQUIRED
2016-09-22 08:54:16,957 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-64) [58e32f2b] Failed in SpmStatusVDS
method
2016-09-22 08:54:16,958 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-64) [58e32f2b] Command
SpmStatusVDSCommand(HostName = pbuovirt2, HostId = d26d3cb1-df70-472e-964b-546ea4dc8bc7,
storagePoolId = eb13e6d4-cf50-46e6-a43a-234862f1adad) execution failed.
Exception: VDSErrorException: VDSGenericException: VDSErrorException:
Failed to SpmStatusVDS, error = (-202, 'Unable to read resource owners',
'Sanlock exception'), code = 100
2016-09-22 08:54:16,960 INFO
[org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
(DefaultQuartzScheduler_Worker-64) [79193574] Running command:
SetStoragePoolStatusCommand internal: true. Entities affected : ID:
eb13e6d4-cf50-46e6-a43a-234862f1adad Type: StoragePool
2016-09-22 08:54:16,962 INFO
[org.ovirt.engine.core.vdsbroker.storage.StoragePoolDomainHelper]
(DefaultQuartzScheduler_Worker-64) [79193574] Storage Pool
eb13e6d4-cf50-46e6-a43a-234862f1adad - Updating Storage Domain
3511c340-acbb-4c40-aeb2-9f4727107a46 status from Active to Unknown,
reason : null
2016-09-22 08:54:16,968 WARN [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_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).
2016-09-22 08:54:17,355 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(DefaultQuartzScheduler_Worker-6) VM child1-leema 29ab1bb4-235d-4b47-ad6a-aa7709020327
moved from NotResponding --> Up
2016-09-22 08:54:26,992 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-64) [79193574] Failed in SpmStatusVDS
method
2016-09-22 08:54:26,997 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-64) [79193574] Command
SpmStatusVDSCommand(HostName = pbuovirt2, HostId = d26d3cb1-df70-472e-964b-546ea4dc8bc7,
storagePoolId = eb13e6d4-cf50-46e6-a43a-234862f1adad) execution failed.
Exception: VDSErrorException: VDSGenericException: VDSErrorException:
Failed to SpmStatusVDS, error = (-202, 'Sanlock resource read failure',
'Sanlock exception'), code = 100
2016-09-22 08:54:26,997 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData]
(DefaultQuartzScheduler_Worker-64) [79193574] hostFromVds::selectedVds -
pbuovirt2, spmStatus returned null!
^C
[root@pscloud ~]#
On Wed, Sep 21, 2016 at 6:19 PM, Kevin Goldblatt <kgoldbla(a)redhat.com>
wrote:
> Hi Badur,
>
>
>
> I would like to understand what you are trying to configure.
>
> Are you trying to expose a LUN to your vdsm host to use in order to
> create an ISCSI storage domain?
> If so please verify the following:
>
> 1. Have you correctly mapped the LUN to your vdsm host initiator via your
> storage provider
>
> 2. Is the LUN visible via the vdsm host. For this run:
> a. "multipath -ll" on the vdsm host. Your output for a LUN should look
> something like this:
>
> xxxxxxxxxxxx1600024 dm-6 XxxxxIO ,XxxxxApp
> size=80G features='0' hwhandler='0' wp=rw
> `-+- policy='queue-length 0' prio=1 status=active
> |- 0:0:0:8 sdh 8:112 active ready running
> |- 0:0:1:8 sdp 8:240 active ready running
> |- 5:0:0:8 sdx 65:112 active ready running
> `- 5:0:1:8 sdaf 65:240 active ready running
>
> 3. Have you edited your /etc/iscsi/initiatorname.iscsi
> You should have something like this:
> InitiatorName=iqn.1xxx-xx.com.redhat:host1-vds1 (replace the string
> after the : with the iqn given in the storage provider)
>
>
> 4. Reboot your host after making any changes
>
>
> 5. Once you the LUN is visible to the host you can create a Storage
> Domain via the Ovirt GUI"
> a. Select the ISCSI Storage Type
> b. Discover the Targets by using one of the IP addresses of the storage
> provider Ports
>
> Hope this helps,
>
>
>
> Regards,
>
>
> Kevin
>
>
> On Tue, Sep 20, 2016 at 12:54 PM, Budur Nagaraju <nbudoor(a)gmail.com>
> wrote:
>
>> HI All,
>>
>> While configuring iSCSI LUN is not getting detected any documents to
>> configure iSCSI in oVirt ?
>>
>> Thanks,
>> Nagaraju
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>