[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4010.
-----------------------------
Closing then.
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Sudhir Verma
> Assignee: Sudhir Verma
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
> *Update*
> Better to use systeminfo command. Here is example of output:
> {code}$ systeminfo
> Host Name: ESKIMO-ASUS
> OS Name: Microsoft Windows 10 Pro
> OS Version: 10.0.14393 N/A Build 14393
> OS Manufacturer: Microsoft Corporation
> OS Configuration: Standalone Workstation
> OS Build Type: Multiprocessor Free
> Registered Owner: eskimo
> Registered Organization:
> Product ID: 00330-80000-00000-AA020
> Original Install Date: 9/26/2016, 4:15:45 AM
> System Boot Time: 12/19/2016, 4:23:14 PM
> System Manufacturer: ASUSTeK Computer Inc.
> System Model: G53SX
> System Type: x64-based PC
> Processor(s): 1 Processor(s) Installed.
> [01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~2201 Mhz
> BIOS Version: American Megatrends Inc. G53SX.203, 7/5/2011
> Windows Directory: C:\WINDOWS
> System Directory: C:\WINDOWS\system32
> Boot Device: \Device\HarddiskVolume1
> System Locale: en-us;English (United States)
> Input Locale: en-us;English (United States)
> Time Zone: (UTC-08:00) Pacific Time (US & Canada)
> Total Physical Memory: 16,361 MB
> Available Physical Memory: 10,150 MB
> Virtual Memory: Max Size: 32,745 MB
> Virtual Memory: Available: 23,976 MB
> Virtual Memory: In Use: 8,769 MB
> Page File Location(s): C:\pagefile.sys
> Domain: WORKGROUP
> Logon Server: \\ESKIMO-ASUS
> Hotfix(s): 7 Hotfix(s) Installed.
> [01]: KB3176935
> [02]: KB3176936
> [03]: KB3176937
> [04]: KB3199209
> [05]: KB3199986
> [06]: KB3209498
> [07]: KB3206632
> Network Card(s): 3 NIC(s) Installed.
> [01]: Qualcomm Atheros AR9002WB-1NG Wireless Network Adapter
> Connection Name: Wi-Fi
> DHCP Enabled: Yes
> DHCP Server: 192.168.0.1
> IP address(es)
> [01]: 192.168.0.101
> [02]: Realtek PCIe GBE Family Controller
> Connection Name: Ethernet
> Status: Media disconnected
> [03]: Cisco Systems VPN Adapter for 64-bit Windows
> Connection Name: Ethernet 3
> DHCP Enabled: No
> IP address(es)
> [01]: 10.3.230.99
> [02]: fe80::e40c:d8f4:d1f6:5959
> Hyper-V Requirements: VM Monitor Mode Extensions: Yes
> Virtualization Enabled In Firmware: Yes
> Second Level Address Translation: Yes
> Data Execution Prevention Available: Yes
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4058.
-----------------------------
Closing as outdated.
> Installer does not validate VAGRANT_HOME when used
> --------------------------------------------------
>
> Key: JBDS-4058
> URL: https://issues.jboss.org/browse/JBDS-4058
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents.
> Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4062.
-----------------------------
Closing as outdated (vagrant removal in the next release).
> 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)
8 years, 8 months
[JBoss JIRA] (JBDS-4081) Installation fails with "Error: Command failed: vagrant box remove cdkv2 -f" when a previous installation went bad
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4081?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4081.
-----------------------------
Closing as outdated.
> 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)
8 years, 8 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-4257:
--------------------------------------
[~nickboldt], I'm afraid this is some kind of misunderstanding. This ticket is about rh-eclipse46-devstudio.rpm having too many Provides. That leads to accidents where rh-eclipse46-devstudio.rpm is dragged as a dependency for some other RPMs.
In other words, in this ticket we do not discuss what Devstudio needs but what it unnecessarily provides ("advertises") in its RPM declaration.
{{rpm -q --provides -p ./rh-eclipse46-devstudio-10.3-0.20170129.1911.el7.x86_64.rpm}} lists 500+ items while only few make sense in our situation. There should be
* rh-eclipse46-devstudio = 10.3-0.20170129.1911.el7
* rh-eclipse46-devstudio(x86-64) = 10.3-0.20170129.1911.el7
This is all. We can safely add several others (rh-eclipse46-osgi(com.jboss.devstudio.*)). The rest don't have any use now but can create troubles (like the one [~lvalach] experienced).
> rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
> ------------------------------------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík edited comment on JBDS-4257 at 1/31/17 3:18 AM:
---------------------------------------------------------------
[~nickboldt], I'm afraid this is some kind of misunderstanding. This ticket is about rh-eclipse46-devstudio.rpm having too many Provides. That leads to accidents where rh-eclipse46-devstudio.rpm is dragged as a dependency for some other RPMs.
In other words, in this ticket we do not discuss what Devstudio needs but what it unnecessarily provides ("advertises") in its RPM declaration.
{{rpm -q --provides -p ./rh-eclipse46-devstudio-10.3-0.20170129.1911.el7.x86_64.rpm}} lists 500+ items while only few make sense in our situation. There should be
* rh-eclipse46-devstudio = 10.3-0.20170129.1911.el7
* rh-eclipse46-devstudio(x86-64) = 10.3-0.20170129.1911.el7
This is all. We can safely add several others (rh-eclipse46-osgi(com.jboss.devstudio.*)). The rest don't have any use now but can create troubles (like the one [~lvalach] experienced).
was (Author: vkadlcik):
[~nickboldt], I'm afraid this is some kind of misunderstanding. This ticket is about rh-eclipse46-devstudio.rpm having too many Provides. That leads to accidents where rh-eclipse46-devstudio.rpm is dragged as a dependency for some other RPMs.
In other words, in this ticket we do not discuss what Devstudio needs but what it unnecessarily provides ("advertises") in its RPM declaration.
{{rpm -q --provides -p ./rh-eclipse46-devstudio-10.3-0.20170129.1911.el7.x86_64.rpm}} lists 500+ items while only few make sense in our situation. There should be
* rh-eclipse46-devstudio = 10.3-0.20170129.1911.el7
* rh-eclipse46-devstudio(x86-64) = 10.3-0.20170129.1911.el7
This is all. We can safely add several others (rh-eclipse46-osgi(com.jboss.devstudio.*)). The rest don't have any use now but can create troubles (like the one [~lvalach] experienced).
> rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
> ------------------------------------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months