You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you noted in the Vagrant issue, vagrant winrm-config, while returning the properly forwarded winrm port, doesn't return the updated rdp port as it doesn't know about it. This is really a bug/enhancement for kitchen-vagrant and I filed test-kitchen/kitchen-vagrant#224 for it.
Description
When the default RDP port of 3306 is in use and vagrant automatically forwards to a different port the
kitchen login
command stops working.I opened this ticket with vagrant but I'm lead to believe this might be a test-kitchen issue:
hashicorp/vagrant#7174
Kitchen Version
I started in the 1.4.x
I then upgraded to 1.5.x and 1.6.0 in an attempt to fix the issue.
ChefDK Version
Chef Development Kit Version: 0.11.2
chef-client version: 12.8.1
berks version: 4.3.2
kitchen version: 1.6.0
Platform Version
Windows 7 64-bit
Replication Case
Run:
berks cookbook bugtest
Then update kitchen.yml file to look like:
Run:
kitchen create
You will then see this in the output:
==> default: Fixed port collision for 3389 => 33389. Now on port 2220.
Then try:
kitchen login
You will see that it always attempts to connect to port 3389.
Kitchen Output
if you look at the file .kitchen/default-win2012.yml that is created you will see it lists rdp_port as 3389.
Kitchen Diagnose
https://gist.github.com/wstaples/7cb31cbf2b7d79ac436b52e6f1ea36c8
The text was updated successfully, but these errors were encountered: