[JBoss JIRA] (JBDS-4064) CDK installation failed with error 'box already exists' in case existing install done by different user
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4064?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4064:
--------------------------------
Sprint: devex #126 January 2017
> CDK installation failed with error 'box already exists' in case existing install done by different user
> -------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4064
> URL: https://issues.jboss.org/browse/JBDS-4064
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Environment: *Operating System*
> Windows 10 Pro 64 Bit
> *Devsuite version*
> Devsuite 1.1.0-GA
> Reporter: Budh Ram Gurung
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.3.0.AM2
>
> Attachments: install_log_sept_27.txt
>
>
> After referring through the [devsuite-installation guide#CDK Installation Failure|http://jenkinscat.gsslab.pnq.redhat.com:8080/view/Devtools/job/doc-devsuite_Installation%20Guide%20%28html-single%29/lastSuccessfulBuild/artifact/index.html#_cdk_installation_failure] for CDK installation failure which says install *Microsoft Visual C++ 2010 Redistributable Package (x86)* and reinstall the installer, my CDK installation failed even after having above package and reinstalling the installer.
> I am expecting that devsuite should handle the already existing box automatically.
> Does it mean we should update the documentation saying "uninstall the previous devsuite installation" which will remove everything including box and then reinstall the installer?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4081) Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4081?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4081:
--------------------------------
Sprint: devex #126 January 2017
> Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4081
> URL: https://issues.jboss.org/browse/JBDS-4081
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> {noformat}
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f
> Tue, 04 Oct 2016 13:08:46 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "DESKTOP-9NT300B",
> "ComSpec": "C:\\WINDOWS\\system32\\cmd.exe",
> "DOCKER_CERT_PATH": "C:\\certificate",
> "DOCKER_HOST": "tcp://10.1.2.2:2376",
> "DOCKER_MACHINE_NAME": "498b304",
> "DOCKER_TLS_VERIFY": "1",
> "DOCKER_TOOLBOX_INSTALL_PATH": "C:\\Program Files\\Docker Toolbox",
> "GIT_HOME": "C:\\Program Files\\Git",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\Aurelien Pupier",
> "JAVA_HOME": "C:\\Program Files\\Java\\jdk1.8.0_65",
> "LOCALAPPDATA": "C:\\Users\\Aurelien Pupier\\AppData\\Local",
> "LOGONSERVER": "\\\\DESKTOP-9NT300B",
> "MAVEN_HOME": "C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9",
> "NUMBER_OF_PROCESSORS": "8",
> "OS": "Windows_NT",
> "Path": "C:\\ProgramData\\Oracle\\Java\\javapath;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\Program Files (x86)\\Skype\\Phone\\;C:\\Program Files (x86)\\PuTTY\\;C:\\Program Files\\RedHat\\java-1.8.0-openjdk-1.8.0.102-1\\bin;C:\\HashiCorp\\Vagrant\\bin;c:\\install\\DevelopmentSuite\\cdk\\bin;c:\\install\\DevelopmentSuite\\cygwin\\bin;C:\\OpenShift;C:\\Program Files\\Docker Toolbox;C:\\install\\apache-maven-3.3.9-bin\\apache-maven-3.3.9\\bin;C:\\Program Files\\Git\\bin;C:\\Users\\Aurelien Pupier\\AppData\\Local\\Microsoft\\WindowsApps;C:\\HashiCorp\\Vagrant\\bin;bin;C:\\Program Files\\Oracle\\VirtualBox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 3, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c03",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Program Files\\WindowsPowerShell\\Modules;C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\Modules",
> "PUBLIC": "C:\\Users\\Public",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\WINDOWS",
> "TEMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\AURELI~1\\AppData\\Local\\Temp",
> "USERDOMAIN": "DESKTOP-9NT300B",
> "USERDOMAIN_ROAMINGPROFILE": "DESKTOP-9NT300B",
> "USERNAME": "Aurelien Pupier",
> "USERPROFILE": "C:\\Users\\Aurelien Pupier",
> "VAGRANT_DETECTED_OS": "cygwin",
> "VAGRANT_HOME": "C:\\install\\.vagrant_home",
> "VBOX_MSI_INSTALL_PATH": "C:\\Program Files\\Oracle\\VirtualBox\\",
> "windir": "C:\\WINDOWS",
> "__COMPAT_LAYER": "Installer"
> },
> "cwd": "c:\\install\\DevelopmentSuite-1.1.0\\cdk\\boxes"
> }
> Tue, 04 Oct 2016 13:08:48 GMT-ERROR: cdk - Error: Command failed: vagrant box remove cdkv2 -f
> [0;31mThe VirtualBox VM was created with a user that doesn't match the
> current user running Vagrant. VirtualBox requires that the same user
> be used to manage the VM that was created. Please re-run Vagrant with
> that user. This is not a Vagrant issue.
> The UID used to create the VM was: 0
> Your UID is: 1001
> {noformat}
> I tried to call the same command from cmd line and I have the same error.
> I tried to call the same command from cmd line as administrator and I have the same error.
> I found this on StackOverflow:http://stackoverflow.com/questions/31644222/vagrant-not-sta... but I have no .vagrant\machines\default\virtualbox\creator_uid files neither .vagrant folder, I have only .vagrant.d folder
> I'm on Windows 10
> I suppose that the previous version of the box was installed while I followed the steps to install CDK before the installer exists.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4038) Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4038?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4038:
--------------------------------
Sprint: devex #126 January 2017
> Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character
> ---------------------------------------------------------------------------------------------------
>
> Key: JBDS-4038
> URL: https://issues.jboss.org/browse/JBDS-4038
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Environment: Windows 7 Pro, x86_64, SP1
> Reporter: Ondrej Dockal
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.3.0.AM2
>
>
> Default installation on Non-ASCII path fails to install/configure CDK.
> Error from install log file:
> Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem"
> Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute options {
> "env": {
> "ALLUSERSPROFILE": "C:\\ProgramData",
> "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming",
> "CommonProgramFiles": "C:\\Program Files\\Common Files",
> "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files",
> "CommonProgramW6432": "C:\\Program Files\\Common Files",
> "COMPUTERNAME": "SOME-PC",
> "ComSpec": "C:\\Windows\\system32\\cmd.exe",
> "FP_NO_HOST_CHECK": "NO",
> "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q",
> "HOMEDRIVE": "C:",
> "HOMEPATH": "\\Users\\jbossqa",
> "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local",
> "LOGONSERVER": "\\\\SOME-PC",
> "NUMBER_OF_PROCESSORS": "2",
> "OS": "Windows_NT",
> "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;c:\\DevelopmentÅ uite\\cdk\\bin;c:\\DevelopmentÅ uite\\vagrant\\bin;c:\\DevelopmentÅ uite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;;c:\\DevelopmentŠuite\\vagrant\\bin;c:\\DevelopmentŠuite\\cygwin\\bin;C:\\DevelopmentŠuite\\virtualbox\\",
> "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC",
> "PROCESSOR_ARCHITECTURE": "AMD64",
> "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel",
> "PROCESSOR_LEVEL": "6",
> "PROCESSOR_REVISION": "3c01",
> "ProgramData": "C:\\ProgramData",
> "ProgramFiles": "C:\\Program Files",
> "ProgramFiles(x86)": "C:\\Program Files (x86)",
> "ProgramW6432": "C:\\Program Files",
> "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\",
> "PUBLIC": "C:\\Users\\Public",
> "SESSIONNAME": "Console",
> "SystemDrive": "C:",
> "SystemRoot": "C:\\Windows",
> "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp",
> "USERDOMAIN": "Some-PC",
> "USERNAME": "jbossqa",
> "USERPROFILE": "C:\\Users\\jbossqa",
> "VAGRANT_DETECTED_OS": "cygwin",
> "windir": "C:\\Windows",
> "windows_tracing_flags": "3",
> "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log",
> "__COMPAT_LAYER": "VistaSetup"
> },
> "cwd": "c:\\DevelopmentŠuite\\cdk\\boxes"
> }
> Thu, 01 Sep 2016 11:19:25 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem"
> <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError)
> from <internal:gem_prelude>:1:in `<compiled>'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4062:
--------------------------------
Sprint: devex #126 January 2017
> Error about space in User's Profile location (home) folder should be reported on confirmation page
> --------------------------------------------------------------------------------------------------
>
> Key: JBDS-4062
> URL: https://issues.jboss.org/browse/JBDS-4062
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> Considering every component from currently provided stack is optional for installation there is no reason to block installation process on Target Install Folder selection page in case user has space in his profile folder name (home folder). It should be reported on Confirmation page when vagrant is selected for install. It should not block installation for OpenJDK and DevStudio only.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Sprint: devex #126 January 2017
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.3.0.AM2
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3956) Installer should let to update detected oracle vurtualbox
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3956?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3956:
--------------------------------
Summary: Installer should let to update detected oracle vurtualbox (was: Installer should let to update detected oracle vurtualbox and vagrant)
> Installer should let to update detected oracle vurtualbox
> ---------------------------------------------------------
>
> Key: JBDS-3956
> URL: https://issues.jboss.org/browse/JBDS-3956
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> It should also work for OpenJDK installed from .msi file. Detection should read installation information from registry using vbs scripts (see https://msdn.microsoft.com/en-us/library/aa369767(v=vs.85).aspx for details).
> Reading install information form registry would work better than detection based on environment variables. It would let rerun detection on installer windows activation and detect changes in configuration without restarting installer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months