[jira] [Commented] (CLOUDSTACK-5662) XenServer can't discover iSCSI targets with different credentials

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857694#comment-13857694 ] 

ASF subversion and git services commented on CLOUDSTACK-5662:
-------------------------------------------------------------

Commit 574fc3a4f8fa5927b488f817f99ff33a91eccd10 in branch refs/heads/4.3 from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=574fc3a ]

CLOUDSTACK-5662: XenServer can't discover iSCSI targets with different credentials


> XenServer can't discover iSCSI targets with different credentials
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5662
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5662
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: XenServer 6.1
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For: 4.3.0
>
>
> If you discover an iSCSI target using CHAP credentials, say, x and later want to discover another iSCSI target using CHAP credentials, says, y, the second iSCSI target cannot be discovered because XenServer only tries to discover iSCSI targets using CHAP credentials x (which are the first CHAP credentials XenServer encountered for the portal in question).
> This is a problem for a multi-tenant storage system and I have seen this issue when using the SolidFire plug-in.
> The SolidFire plug-in needs to be changed to stop using CHAP with XenServer and instead use its Volume Access Group feature (which maps host IQNs to volumes).
> This will also require changes in CloudStack itself.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)