[jira] [Commented] (JCLOUDS-337) 'unrecognized' volume state when trying to attach several volumes to an instance

["Chris Custine (JIRA)" <ji...@apache.org>]

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

Chris Custine commented on JCLOUDS-337:
---------------------------------------

I tried, but was unable to reproduce this.  It is possible that the bug was fixed by recent updates to the HP Cloud provider, or it could have been fixed in HP Cloud itself.  If you are still monitoring this issue, please try with the latest 1.8.0-SNAPSHOT or 1.7.4-SNAPSHOT builds and update this issue with some sample code if it still occurs.

> 'unrecognized' volume state when trying to attach several volumes to an instance
> --------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-337
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-337
>             Project: jclouds
>          Issue Type: Bug
>            Reporter: matthew wagoner
>
> It seems that after attaching several volumes to a single instance in parallel, sometimes an 'unrecognized' volume-status is received when querying volume status after the attach operation. 
> This although the volumes are created in parallel as well, and always get a good status when querying volume-status after creation (status 'available'). 
> Moreover, it seems that trying to query the volume-status of problematic volumes again, a good 'in-use' status is received (which means the volume was attached successfully). 
> Also important to mention, is that this behavior is not present when attaching volumes in a serial order / in parallel, but to different instances. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)