[
https://issues.apache.org/jira/browse/LIBCLOUD-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749236#comment-13749236
]
Tomaz Muraus commented on LIBCLOUD-371:
---------------------------------------
[~sengork] I think we should go with either #2 or #3.
If there are any other resources created before this exception is potentially
thrown we should try to re-order the operations (if possible) so this exception
happens as soon as possible and things aren't left in an inconsistent state.
And yeah, cleaning up xpath and exception reporting would be great. Feel free
to open a separate ticket for this.
> vcloud.py:1414 restricts vm names to 15 chars, however, this limitation is
> windows only.
> ----------------------------------------------------------------------------------------
>
> Key: LIBCLOUD-371
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-371
> Project: Libcloud
> Issue Type: Bug
> Components: Compute, Core
> Affects Versions: 0.12.3
> Environment: LibCloud 0.13
> Reporter: Brian Mingus
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> vcloud.py:1514 if len(name) > 15: raise ValueError('The VM name "' + name +
> '" is too long for the computer name (max 15 chars allowed).')
> This is only true for windows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
