CDK 2.1 seems to have a problem installing

[ken.chenis]

When I go through the install, everything seems to work and "succeed", but the next steps in the process/instructions don't work

• There is no cdk menu items or capabilities in JBoss Dev Studio
• There is no openshift box running in virtualbox (or imported)

If I follow the manual install instructions to get the box into virtualbox, when I do vagrant up, it fails with an rsync issue:

==> default: Copying TLS certificates to C:/a_system/DevelopmentSuite/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtual box/docker

==> default: Rsyncing folder: /cygdrive/c/a_system/DevelopmentSuite/cdk/components/rhel/rhel-ose/ => /vagrant

There was an error when attempting to rsync a synced folder.

Please inspect the error message below for more info.

Host path: /cygdrive/c/a_system/DevelopmentSuite/cdk/components/rhel/rhel-ose/

Guest path: /vagrant

Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync

-e ssh -p 2222 -o ControlMaster=auto -o ControlPath=C:/Users/chenisk/AppData/Local/Temp/ssh.871 -o ControlPersist=10m -o StrictHost

KeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/a_system/DevelopmentSuite/cdk/components/rhel/rhel-ose/

.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /cygdrive/c/a_system/DevelopmentSuite/cdk/components/rhel/rhel

-ose/ vagrant@127.0.0.1:/vagrant

Error: Could not create directory '/home/chenisk/.ssh'.

Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.

mm_receive_fd: no message header

process_mux_new_session: failed to receive fd 0 from slave

mux_client_request_session: read from master failed: Connection reset by peer

Failed to connect to new control master

rsync: connection unexpectedly closed (0 bytes received so far) [sender]

rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]

where is it trying to create this /home/chenisk/.ssh directory?  In the container?  Thoughts on how to get around this error?   How do I get the JBoss Dev Tools updated so the CDK capabilities are there?

For reference, I did an install on Windows 7 64bit with development-suite-1.0.0-GA-bundle-installer.exe    I've done this a couple times, and get the same results each time.

Thanks!

[nickboldt]

Can you create a folder in c:\home\chenisk\.ssh ? or in C:\Users\chenisk\.ssh\ ?

I think cygwin's rsync is trying to create a ~/.ssh/known_hosts file.

[dgolovin1]

It tries to create .ssh on your local drive here /cygdrive/c/a_system/DevelopmentSuite/home/chenisk/.

[ken.chenis]

That folder and file already exist in that directory:

chenisk@DL-R90J9PW8 ~

$ cd .ssh

chenisk@DL-R90J9PW8 ~/.ssh

$ ls

known_hosts

chenisk@DL-R90J9PW8 ~/.ssh

$ more known_hosts

master.ose.am.tsacorp.com,10.13.22.36 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbm

lzdHAyNTYAAAAIbmlzdHAyNTYAAABBBIGEZPgjy8hNy0STb6pRPiYiebYQi9iPk86Mmb1ECjGX44lYys

Ax6yrbDDdqvv4Mtde0i7tiAvXCfau01UMCKTg=

chenisk@DL-R90J9PW8 ~/.ssh

[dgolovin]

Correction, right location is: /cygdrive/c/a_system/DevelopmentSuite/cygwin/home/chenisk/ Could you check if you have permissions to modify this folder?

[jeffmaury]

You should run vagrant up from a cmd command shell and not from a cygwin shell ? Do you ?

[ken.chenis]

There is no "chenisk" directory at /cygdrive/c/a_system/DevelopmentSuite/cygwin/home - the home directory is there, but no users in it... I DO have permission to create folders here though, so it is not a permission issue.   Not sure what part of the install would be creating the chenisk directory there... when I launch cygwin and go to /home/chenisk it is NOT the directory at /cygdrive/c/a_system/DevelopmentSuite/cygwin/home.

[dgolovin]

What is the output for cygwin -w /home/chenisk ?

[dgolovin]

It can be executed from any terminal on windows, it should just work and it does for me in cygwin, cmd and powershell.

[ken.chenis]

OK, I think I found the issue (and a new one) - will post how I got around it.

The machine had a previous cygwin install already that was not detected by the installer, so it installs a second one - this creates confusion because we end up with 2 cygwin environments, one that I guess works from the command shell, and one that is referenced by the tool - depending on path order you can get different cygwin instances.

Figuring I wanted to remove as many issues as possible, I removed all auxiliary software other than virtualbox and re-installed taking all the default settings for directories and such.

When doing this, it fails in a different place when you try to do a vagrant up because it tries to use a Windows 8 feature called "Hyper-V cmdlets for PowerShell" (and I have Windows 7).  Did some research on this error, and found the work-around for this is to upgrade to a newer version of Vagrant, so I upgraded to the latest (1.8.5)

Retried vagrant up, but this fails because Vagrant 1.8.5 has some issue with the SSH key change-over, so it swaps out the ssh key, then locks itself out of the box.   Research on this shows it is a bug in 1.8.5 and the work-arounds are downgrade to 1.8.4, or add "config.ssh.insert_key = false" to the vagrantfile.  I chose the latter (give that each vagrant upgrade/downgrade requires rebooting)

Edit the Vagrantfile, then vagrant destroy and again vagrant up...

All working...

Openshift is up and running, I can connect from the console, web, and IDE...

Thanks for your help.

[dgolovin]

Cygwin detection issue is already reported here https://issues.jboss.org/browse/JBDS-3862 and should be fixed soon. Thank you for update about workaround for this issue!