[JBoss JIRA] (JBDS-3742) Cygwin setup executable should be installed as well
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3742?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3742:
--------------------------------
Status: New (was: New)
Target Release: 9.1.0.GA
> Cygwin setup executable should be installed as well
> ---------------------------------------------------
>
> Key: JBDS-3742
> URL: https://issues.jboss.org/browse/JBDS-3742
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Hardy Ferentschik
> Priority: Minor
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Component/s: installer
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Summary: when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed (was: when replacing an existing VBos install, should use the same install folder; could also ask user where they want VirtualBox installed)
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3761) when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3761?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3761:
-----------------------------
Fix Version/s: 9.1.0.GA
> when replacing an existing VBox install, should use the same install folder; could also ask user where they want VirtualBox installed
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3761
> URL: https://issues.jboss.org/browse/JBDS-3761
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 9.1.0.GA
>
> Attachments: vbox-install-omits-guestadditions.png
>
>
> I had Virtual Box 5.0.16 installed.
> The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the default folder, c:\Program Files\Oracle\VirtualBox.
> As a result, my existing VB install cannot find the Guest Additions iso image.
> !vbox-install-omits-guestadditions.png!
> I suggest that since the installation of Virtual Box isn't something that is necessarily tied into the DevPlatform, it should be installed into its default folder, c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
> Or if not, the installer could ask the user if they want to use the default folder (for reuse) or install under the DeveloperPlatform folder (for a more self-contained installation footprint).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3766:
------------------------------------
This error was reported in response to "vagrant up" with the attempted installation:
{code}
C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant global-status
id name provider state directory
---------------------------------------------------------------------------------------
dd89029 default virtualbox poweroff C:/DeveloperPlatform/cdk/components/rhel/rhel-ose
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["modifyvm", "0a2f3c37-c477-4682-bb9b-41745b76dcea", "--natpf1", "delete", "ssh"]
Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "LockMachine(a->session, LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp
{code}
Performing a system restart resolved the issue.
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: 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
(v6.4.11#64026)
10 years
[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 Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3766:
-------------------------------
Summary: Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the vagrant log? (was: Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?)
> 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: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3766:
--------------------------------
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: 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
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3766) Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3766?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3766:
-------------------------------
Attachment: install.log
vbox.log
vagrant.log
> Installer - Seeing an intermittent issue where vagrant fails to start - is a system restart needed as indicated in the log?
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3766
> URL: https://issues.jboss.org/browse/JBDS-3766
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Installer: Setup-bundled-0.0.2-20160401-33
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: 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
(v6.4.11#64026)
10 years