cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8826) XenServer - Use device id passed as part of attach volume API properly
Date Tue, 22 Sep 2015 10:16:05 GMT

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

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

Commit 86325cbc95abfff038e7929ac8c8d3b3b3bd0267 in cloudstack's branch refs/heads/master from
[~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=86325cb ]

Merge pull request #792 from koushik-das/CLOUDSTACK-8826

CLOUDSTACK-8826: XenServer - Use device id passed as part of attach volume API properly

If device id passed as part of API and available then use it otherwise fallback on XS to automatically
assign one.
For ISO device id used is 3 and it is processed before any other entry to avoid conflict.

Signed-off-by: Koushik Das <koushik@apache.org>


> XenServer - Use device id passed as part of attach volume API properly
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8826
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8826
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.6.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.6.0
>
>
> Random failures were seen in XS attach/detach volume test scenarios (many attach/detach
were performed on the same VM over a span of 24 hrs).
> The failures happened as the device id for attaching volume wasn't available in HV. Some
detached volume didn't got cleaned up properly and so the device id wasn't released.
> The fix would be clean up stale volumes before attaching new ones so the device slots
are released. Also using the device id should be best effort and if that particular id is
not available in XS, it should fallback on using an id that is available and automatically
assigned.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message