-
Bug
-
Resolution: Done
-
Critical
-
4.5.2.Final
-
None
When CDK is being run via jenkins on windows slaves, we can see that improper ssh is used to connect to rhel guest, and command that follows will fail:
ie.:
14:17:12 &{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker@127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\Admin\.minishift\machines\minishift\id_rsa -p 49784] C:\ProgramData\chocolatey\bin\ssh.exe <nil>} 14:17:12 About to run SSH command: 14:17:12 printf '%s' '-----BEGIN CERTIFICATE----- 14:17:12 MIICzTCCAbWgAwIBAgIQIo4gxNYty+nXDs+ketnGKDANBgkqhkiG9w0BAQsFADAQ ... lwvqfWHvZ3Jo94PygMlhLQTWVMVpXAIBdx8ypeeVyMhcUuPJDa01nhPr3nhMBKPj 14:17:12 fg== 14:17:12 -----END CERTIFICATE----- 14:17:12 ' | sudo tee /etc/docker/ca.pem 14:17:12 SSH cmd err, output: exit status 1: bash: -c: line 0: unexpected EOF while looking for matching `'' 14:17:12 bash: -c: line 1: syntax error: unexpected end of file 14:17:12 14:17:14 FAIL E0103 14:17:14.245649 4008 start.go:364] Error starting the VM: Error creating the VM. Error creating machine: Error running provisioning: ssh command error
This is because CDK will use first ssh on windows path. Fix for this could be position proper ssh (one from cygwin64 installation) on the path beginning.