Opened 10 years ago

Closed 9 years ago

#66 closed (fixed)

Custom image creation fails on ops

Reported by: Owned by: somebody
Priority: major Milestone:
Component: AM Version: SPIRAL5
Keywords: Cc:


While trying to create a custom image on the ops nodes ran into problems. First,

[lnevers@ops ~]$ ./ -n rawcust -m CustomF15 --certfile ~/.ssl/emulab.pem 
Traceback (most recent call last):
  File "./", line 46, in <module>
    execfile( "" )
  File "", line 140, in <module>
    cert = M2Crypto.X509.load_cert( CERTIFICATE )
  File "/usr/local/lib/python2.7/site-packages/M2Crypto-0.21.1-py2.7-freebsd-9.0-STABLE-i386.egg/M2Crypto/", line 609, in load_cert
    bio = BIO.openfile(file)
  File "/usr/local/lib/python2.7/site-packages/M2Crypto-0.21.1-py2.7-freebsd-9.0-STABLE-i386.egg/M2Crypto/", line 186, in openfile
    return File(open(filename, mode))
IOError: [Errno 2] No such file or directory: '/users/lnevers/.ssl/encrypted.pem'

Even though a cert-file is specified, the hard-coded one in is still being used. So renamed the existing "~/.ssl/emulab.pem" to the expected "~/.ssl/encrypted.pem, but still fails:

[lnevers@ops ~]$ ./ -n rawcust -m CustomF15
403 Forbidden
Could not get my credential

What am I missing?

  1. Renamed the existing emulab.pem to the expected encrypted.pem.
  1. Re-executed command:
    [lnevers@ops ~]$ ./ -n rawcust -m CustomF15
    403 Forbidden
    Could not get my credential

Change History (2)

comment:1 Changed 10 years ago by

Summary: Custom image creation faila on opsCustom image creation fails on ops

comment:2 Changed 9 years ago by

Resolution: fixed
Status: newclosed

Closing this ticket, the failure was a credentials mismatch.

Note: See TracTickets for help on using tickets.