April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-3799 at 4/13/16 6:21 PM: ------------------------------------------------------------ didn't see the issue today with cdk 1.0.0.CR3 and the latest jbds build, on win10 and osx was (Author: fbricon): didn't see the issue today with cdk 1.0.0.CR3 and the latest jbds build > Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime > ----------------------------------------------------------------------------------------- > > Key: JBDS-3799 > URL: https://issues.jboss.org/browse/JBDS-3799 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Hardy Ferentschik > Priority: Critical > Labels: havoc > > This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272 > Is causing rsync issues such as: > default: Rsyncing folder: /c/DeveloperPlatform/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: /c/DeveloperPlatform/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 StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. > dup() in/out/err failed > 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] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3799: ----------------------------------- didn't see the issue today with cdk 1.0.0.CR3 and the latest jbds build > Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime > ----------------------------------------------------------------------------------------- > > Key: JBDS-3799 > URL: https://issues.jboss.org/browse/JBDS-3799 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Hardy Ferentschik > Priority: Critical > Labels: havoc > > This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272 > Is causing rsync issues such as: > default: Rsyncing folder: /c/DeveloperPlatform/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: /c/DeveloperPlatform/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 StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. > dup() in/out/err failed > 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] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3799: ----------------------------------------- BTW, there is also this issue - https://github.com/projectatomic/adb-atomic-developer-bundle/issues/275 > Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime > ----------------------------------------------------------------------------------------- > > Key: JBDS-3799 > URL: https://issues.jboss.org/browse/JBDS-3799 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Hardy Ferentschik > Priority: Critical > Labels: havoc > > This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272 > Is causing rsync issues such as: > default: Rsyncing folder: /c/DeveloperPlatform/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: /c/DeveloperPlatform/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 StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. > dup() in/out/err failed > 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] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3797: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer: temporary files are not removed when window is closed > ---------------------------------------------------------------- > > Key: JBDS-3797 > URL: https://issues.jboss.org/browse/JBDS-3797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Pavol Pitonak > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > # download installer exe > # run DeveloperPlatformInstaller*.exe > # when installer's window opens, close the window > # look into _C:\Users\yourusername\AppData\Local\Temp_ > result: > Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3639) Update to official OpenShift client binary

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3639?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3639: ----------------------------------- Tested on OSX and it's all good AFAICT. Pod Log, Port Forwarding and RSync work from eclipse (these are the cases we use it) Haven't done any CLI tests > Update to official OpenShift client binary > ------------------------------------------ > > Key: JBDS-3639 > URL: https://issues.jboss.org/browse/JBDS-3639 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Fred Bricon > Labels: havoc > Fix For: 9.1.0.GA > > > Once https://github.com/openshift/origin/pull/6127 is part of an upstream release, modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... with the appropriate URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3638) Update to official CDK v2 release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3638?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3638: -------------------------------------- The PR is replaced by https://github.com/redhat-developer-tooling/developer-platform-install/pu... > Update to official CDK v2 release > --------------------------------- > > Key: JBDS-3638 > URL: https://issues.jboss.org/browse/JBDS-3638 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... to point to the CDK v2 box when a new release is available in Customer Portal. > Also change to use commented out downloadAuth() call for CDK box to provide appropriate authentication: https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3638) Update to official CDK v2 release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3638?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3638: --------------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > Update to official CDK v2 release > --------------------------------- > > Key: JBDS-3638 > URL: https://issues.jboss.org/browse/JBDS-3638 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... to point to the CDK v2 box when a new release is available in Customer Portal. > Also change to use commented out downloadAuth() call for CDK box to provide appropriate authentication: https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-720) JBDS 9.1 GA: Installer - Advise users to enable virt

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-720?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-720: --------------------------------------- https://www.google.com/search?q=enable+virt+in+the+BIOS&ie=utf-8&oe=utf-8... > JBDS 9.1 GA: Installer - Advise users to enable virt > ---------------------------------------------------- > > Key: TOOLSDOC-720 > URL: https://issues.jboss.org/browse/TOOLSDOC-720 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Installation Guide > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: AIO_Installer > > From JBDS-3733: > This might be overkill, but, just in case users are running the installer on a new Windows system, they should be advised that virtualization must be enabled in the BIOS or they will not be able to start vagrant boxes. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-720) JBDS 9.1 GA: Installer - Advise users to enable virt

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-720?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-720: --------------------------------------- It looks like the exact sequence of steps will vary somewhat, depending on the manufacturer of the users' Windows hardware. We should say something like: "In order to run VirtualBox and Vagrant, you must first enable Virtualization in the BIOS settings of your computer. Consult your system's documentation for details on how to change BIOS settings." Something like that or google? ;-) > JBDS 9.1 GA: Installer - Advise users to enable virt > ---------------------------------------------------- > > Key: TOOLSDOC-720 > URL: https://issues.jboss.org/browse/TOOLSDOC-720 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Installation Guide > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: AIO_Installer > > From JBDS-3733: > This might be overkill, but, just in case users are running the installer on a new Windows system, they should be advised that virtualization must be enabled in the BIOS or they will not be able to start vagrant boxes. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-722) JBDS 9.1 GA: Installer - tell users to accept T&C before installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-722?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-722: --------------------------------------- I'd send this to all of dev-tools to review. Thx! > JBDS 9.1 GA: Installer - tell users to accept T&C before installer > ------------------------------------------------------------------ > > Key: TOOLSDOC-722 > URL: https://issues.jboss.org/browse/TOOLSDOC-722 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Installation Guide > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: AIO_Installer > Fix For: 9.1 GA > > > Direct users to accept T&C before using installer: https://issues.jboss.org/browse/JBDS-3723 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016