-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh_key not used with kitchen login #1108
Comments
Could we get an example kitchen.yml and logs? |
|
Normally one does not make the changes directly to .kitchen/instance.yml, these happen in the root .kitchen.yml. For ssh keys, try setting them under the transport key. This could also be an issue with the qemu driver and later version of kitchen. |
No, I did not make changes to the .kitchen/instance.yml. This is set by kitchen-qemu just like it is set by kitchen-vagrant. This used to work until I updated test-kitchen today. |
I see that password is set there as well and this has me suspecting #1095 which will use the password if provided. |
Ah, ok. That makes sense. I'll try to make kitchen-qemu not set state[:password] |
Ok, this fixes it. Thanks! |
Glad we could narrow this down so quickly - the root issue was that we couldn't override a password without this fix and it'd always use SSH key. |
Yeah, it's just a little funny that On the other hand I'm glad it didn't otherwise I wouldn't have seen that test-kitchen switched to using passwords underneath ;) |
Description
My instance has the ssh_key set in the
.kitchen/<instance>.yml
,but
kitchen login <instance>
doesn't seem to use it.Kitchen Version
This happened since I updated to v1.11.1 today. I probably skipped a few version so it could be introduced earlier.
Ruby Version
Standard Arch Linux
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
Platform Version
Arch Linux
Replication Case
Create a new instance with the ssh_key set. Then try
kitchen login <instance>
and see that you'll be prompted for a password.The text was updated successfully, but these errors were encountered: