Closed ashleyz closed 11 years ago
Hi Ashley,
I don't really see what is going wrong. Your env settings look good. The exception comes from this call in the ec2 adaptor:
keypair = conn.ex_describe_keypairs (token)
so the only parameter from SAGA-Python is token
which seems to be set correctly, and is recognized earlier:
2013:07:16 10:26:33 139982509999872 saga.Session : [DEBUG ] adding context : {'Token' : 'effort', 'Type' : 'ec2_keypair', 'UserCert' : '/home/ashley/india/futuregrid_rsa', 'UserID' : 'ubuntu'}
Would you mind checking once more if the UserCert
path is correct? If thst is the case, we need to debug libcloud I'm afraid. Not sure if I should ask you that, but would you mind to wlk through that callstack with a debugger to check on what string variable the lib barfs? No worries if you don't want to, really -- I'll try to reproduce it then, but will probably need some days to get to it...
Best, Andre.
The UserCert path is correct:
(saga-python-env)ashley@effort:~/saga-python$ ls /home/ashley/india/futuregrid_rsa
/home/ashley/india/futuregrid_rsa
(saga-python-env)ashley@effort:~/saga-python$ cat /home/ashley/india/futuregrid_rsa
-----BEGIN RSA PRIVATE KEY-----
... (key info goes here) ...
I will give the debugger a try...
Thanks Ashley! :)
Here is the trace...
...
c2.user_cert = os.environ['EC2_KEYPAIR']
c2.user_id = 'ubuntu' # the user id on the target VM
# we create a session for all SAGA interactions, and attach the respective # security contexts. Those are now avail for all SAGA objects created in
# that session
s = saga.Session (False) # FALSE: don't use any other (default) contexts
s.contexts.append (c1)
s.contexts.append (c2) <----------------- crashes here
Here are the pertinent variables:
c1: {'Server' : 'http://149.165.146.135:8773/services/Eucalyptus', 'Type': 'ec2', 'UserID': '(censored)', 'UserKey' : '(censored)'}
c2: {'Token' : 'effort', 'Type' 'ec2_keypair', 'UserCert':/home/ashley/india/futuregrid_rsa', 'UserID' : 'ubuntu'}
Also session.py:57 is the endpoint at where the error is generated, but it has the information from c2 above...
I think this has been fixed on OSDC side... will reopen if needed.
Hello!
Not sure what is causing the below with the ec2 example invoked from (saga-python-env)ashley@effort:~/saga-python$ python examples/resource/ec2.py) on effort (rock physics machine)
My environment looks like:
which is similar to the environment on a working machine (Sullivan)
Any ideas? :)