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
Interesting. Usually I would not recommend using different versions of the
dependencies. However, I don't recall any particular reasons they might
conflict. Can you give it a try and let me know?
Thanks!
-Zack
From: Jeffrey Nguyen (jeffrngu) [jeffr...@cisco.com]
Usually I would not recommend using different versions of the
dependencies. However, I don't recall any particular reasons they
might conflict.
Definitely would like to repeat that it's not recommended to mix
different versions of jclouds JARs in your app. But of course, we can
always
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 [wid...@gmail.com]
Sent: Thursday, August 14, 2014 1:17 AM
To:
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
I have one key, creatively named Dan Widdis
I'll run some tests with that key renamed and/or deleted.
On 8/14/14, 7:10 AM, Zack Shoylev wrote:
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
Thank you Zack and Andrew. I'll let you know if this works. I'm interested
in the PortApi in particular. I don't know if that is enough to expose any
potential conflicts.
Thanks,
-Jeffrey
From: Zack Shoylev
zack.shoy...@rackspace.commailto:zack.shoy...@rackspace.com
Reply-To:
Or, possibly the name I just gave was just a Rackspace-friendly name.
The one actually in the uploaded key is:
danielwiddis@Daniel-Widdiss-MacBook-Pro.local
On 8/14/14, 7:10 AM, Zack Shoylev wrote:
Hi Dan,
If you go to your myclouds.rackspace.com panel, then go to Servers, under the
SSH
The key data is stored using name-key pairs. My guess is that the problematic
string is the Dan Widdis one, but I am still testing.
-Zack
From: Daniel Widdis [wid...@gmail.com]
Sent: Thursday, August 14, 2014 10:56 AM
To: user@jclouds.apache.org
Subject:
Zack,
I re-uploaded the key, giving it a lowercase name in Rackspace
(dan_widdis) and also all lowercase in my uploaded public key.
But the exception has returned. So I don't think it matters what the
key is named: what matters is the name of the server to which the key is
associated.
Yep, it's not recommended at all.
Using different versions of jclouds in the sane app will bring two
different versions of the jclouds-core to the classpath. The behavior of
*any* jclouds api/provider in this scenario is unpredictable, as
jclouds-core is the one that generates the http requests
So I ran some test with jclouds 1.7.1 and neutron 1.8.0. I got the exception
below when trying to get new ContextBuilder. So this confirmed this
combination doesn't work. I guess the only choice is to upgrade jclouds.
Thanks all for the replies!
java.util.NoSuchElementException: key
If that is still being evaluated against the DnsNameValidator, it is probably
now failing because of the underscore. Try “dan-widdis” and see if that works.
Either way, this is an interesting type of issue that has come up several
times recently so we should probably noodle this a bit and
How would I pass in my new context module?
I've gotten as far as extending S3BlobStoreContextModule,
overriding bucketAcls() to specify a longer expiration, but then what? Do I
just pass in an instance of my context module to ContextBuilder#modules()?
When I tried that, I got this exception:
To be precise, when cleaning up resources, jclouds also cleans up any orphaned
key pairs. However, when it cleans up the keypairs, it validates the key pair
name against the DNS validator. The key pairs are controlled using a key pair
extension, so jclouds validates these values before it
Most of my use of the servers is automated, using dns-compliant server
names (because the code yelled at me a few months ago). I only
encountered this exception doing some manual testing and tweaking and
it's mostly cosmetic, so the workaround for me is to simply ignore the
error and move on!
16 matches
Mail list logo