Hi Dan, If you go to your myclouds.rackspace.com panel, then go to Servers, under the SSH keys tab, what SSH key names do you have? I suspect jclouds expects the SSH key names to have DNS-valid names. Please let me know.
Thanks! ________________________________________ From: Zack Shoylev [[email protected]] Sent: Thursday, August 14, 2014 8:15 AM To: [email protected] Subject: RE: IllegalArgumentException when deleting node on Rackspace Hi Dan, Thanks for following up and for your bug report! I have a couple of ideas why this might be happening, but I am still looking. I'll keep you posted. -Zack ________________________________________ From: Daniel Widdis [[email protected]] Sent: Thursday, August 14, 2014 1:17 AM To: [email protected] Subject: Re: IllegalArgumentException when deleting node on Rackspace Zack, I am able to reproduce this exception at will, using jclouds 1.8.0. The exception appears associated with deleting the very last server on the account, when it has a mixed-case name. This was the ONLY server on my account. I could not get this to reproduce with any other servers running, or even in a creating/deleting/error state. Here is the sequence: 1. Create a server on Rackspace (via website) named "Cloud-Server-01". - If it's relevant, the server was subsequently connected to my managed server network via RackConnect. - If it's relevant, I created from a saved image. 2. Shut down the server using the below code (the ipAddr string passed to the below code was "10.176.1.165") nodes = computeService .destroyNodesMatching(new Predicate<NodeMetadata>() { @Override public boolean apply(final NodeMetadata input) { return input.getPrivateAddresses().contains(ipAddr); } }); Result: java.lang.IllegalArgumentException: Object 'Cloud-Server' doesn't match dns naming constraints. Reason: Should be only lowercase. Stack trace for the deletion-by-IP at: http://pastebin.com/gJ8ti7yX Additionally I can reproduce the exception by destroying server by groupname using computeService.destroyNodesMatching(inGroup("Cloud-Server")). While there is clearly a mixed-case string involved with this test, by the time the code gets to the "cleanup" phase it's only passing around NodeMetaData and not the string. Stack trace for the group deletion: http://pastebin.com/NW76Vms5 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
