]
Denis Golovin updated JBDS-3766:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
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.2.0.AM2
Attachments: install.log, Is_Restart_Needed.png, 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?