kitchen login fails if ssh_key is a relative path.

[markbate]

I'm not entirely sure where this bubbles up from (might be a test-kitchen issue), but kitchen login doesn't seem to like relative paths for ssh keys.

Full path:

- name: ec2-ubuntu-12.04
  driver_name: ec2
  driver_plugin: ec2
  driver_config:
    image_id: ami-ad3660c4 # 64-bit instance-store backed
    username: ubuntu
    ssh_key: ~/Users/markbate/.ec2/test-kitchen.pem

The following should work fine:

kitchen converge default-ec2-ubuntu-1204
kitchen login default-ec2-ubuntu-1204

If you set it a relative path:

- name: ec2-ubuntu-12.04
  driver_name: ec2
  driver_plugin: ec2
  driver_config:
    image_id: ami-ad3660c4 # 64-bit instance-store backed
    username: ubuntu
    ssh_key: ~/.ec2/test-kitchen.pem

The following will converge, but not login.

kitchen converge default-ec2-ubuntu-1204
kitchen login default-ec2-ubuntu-1204

Error message is:

Warning: Identity file ~/.ec2/test-kitchen.pem not accessible: No such file or directory.
Permission denied (publickey).

Tests should also work fine, it's just the login that doesn't expand the path.

[sethvargo]

Marked this as a bug. It might be a TK issue, but paging @fnichol 😄.

[fnichol]

Ah yes, this is something I need to fix/add for drivers, which was added to provisioners.

[sethvargo]

Moved to test-kitchen/test-kitchen#389

[trinitronx]

Workaround for now:

1. Run kitchen login -l debug
D Login command: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o IdentitiesOnly=yes -o LogLevel=VERBOSE -i ~/.ec2/test-kitchen.pem -p 22 ec2-user@ec2-123-456-789-01.compute-1.amazonaws.com (Options: {})
2. Copy Login command
3. Login manually:

ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o IdentitiesOnly=yes -o LogLevel=VERBOSE -i ~/.ec2/test-kitchen.pem -p 22 ec2-user@ec2-123-456-789-01.compute-1.amazonaws.com