Zack, I've updated to 1.8.0 and I'll keep an eye out.
The reason I brought it to light because it seemed like a similar instance to the previous one in which the naming conventions jclouds enforces are more restrictive than the ones permitted by other means of creating the instances, and the code should recognize these situations.
Dan On 8/11/14, 10:29 PM, Zack Shoylev wrote:
Hi Daniel, I am still working on reproducing this, but have not been able to yet. My (generic) advice for now would be to update to the latest jclouds (1.8.0) and let us know if this happens again. I will let you know if we make some progress reproducing this. Also, if I remember correctly, the group is usually based on how the server is named. -Zack
