[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3766.
-------------------------------
Resolution: Out of Date
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log?
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 10.4.0.AM1
>
> Attachments: Is_Restart_Needed.png, install.log, vagrant.log, vbox.log
>
>
> See attached log files.
> After some install attempts, Vagrant fails to start. The vagrant install log reports the following:
> {code}
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant -- Installation completed successfully.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer installed the product. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Installation success or error status: 0.
> MSI (s) (DC:C4) [11:00:34:591]: Windows Installer requires a system restart. Product Name: Vagrant. Product Version: 1.7.4. Product Language: 1033. Manufacturer: HashiCorp. Type of System Restart: 2. Reason for Restart: 2.
> MSI (s) (DC:C4) [11:00:34:591]: Product: Vagrant. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time.
> {code}
> Is a system restart needed to ensure that the vagrant installation is successful on Windows?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3947.
-------------------------------
Resolution: Out of Date
> Some older versions of vagrant skip version validation
> ------------------------------------------------------
>
> Key: JBDS-3947
> URL: https://issues.jboss.org/browse/JBDS-3947
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.4.0.AM1
>
> Attachments: vagrant.png
>
>
> Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though.
> !vagrant.png|thumbnail!
> The issue might be connected to the fact that with these versions the command
> {noformat}where vagrant{noformat}
> in fact returns 2 files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3947:
--------------------------------
Fix Version/s: 10.4.0.AM1
(was: 10.3.0.AM2)
> Some older versions of vagrant skip version validation
> ------------------------------------------------------
>
> Key: JBDS-3947
> URL: https://issues.jboss.org/browse/JBDS-3947
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.4.0.AM1
>
> Attachments: vagrant.png
>
>
> Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though.
> !vagrant.png|thumbnail!
> The issue might be connected to the fact that with these versions the command
> {noformat}where vagrant{noformat}
> in fact returns 2 files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[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 closed JBDS-4081.
-------------------------------
Resolution: Out of Date
> 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.4.0.AM1
>
>
> {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, 1 month
[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 closed JBDS-4064.
-------------------------------
Resolution: Out of Date
> 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.4.0.AM1
>
> 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, 1 month