April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3746) Unable to access OpenShift console with MS Edge

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3746?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3746: --------------------------------- Not assigned to me, but done for docs: https://access.redhat.com/articles/2255391#openshift-console-inaccessible... Do we want to leave this open to track any other part of this task or close it off after assigning it to me? > Unable to access OpenShift console with MS Edge > ------------------------------------------------ > > Key: JBDS-3746 > URL: https://issues.jboss.org/browse/JBDS-3746 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Environment: Windows 10 Pro > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 9.1.0.GA > > > On Windows 10 (Pro) after installing and starting the CDK development environment, one is not able to access the OpenShift console (https://10.1.2.2:8443/console) using Microsoft Edge. The IP of the host only network IP does not matter. Using a 192.168 address won't work either. > Using any other browser - IE, Chrome, Firefox - the console can be reached. It seems to be an Edge specific issue and may report the same issue: > * http://www.tenforums.com/installation-setup/8979-dont-forget-edge-can-acc... > * https://social.technet.microsoft.com/Forums/forefront/en-US/0face535-3c7a... > * https://www.google.se/search?q=edge+canot+acess+page&ie=utf-8&oe=utf-8&gw... > I tried several work-arounds, but none worked so far. If there were a confirmed workaround one could image the installer applying it (if possible). In this case we might want to add a warning somewhere in the installer or at least somewhere in the documentation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3746) Unable to access OpenShift console with MS Edge

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3746?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3746: ---------------------------- Fix Version/s: 9.1.0.GA > Unable to access OpenShift console with MS Edge > ------------------------------------------------ > > Key: JBDS-3746 > URL: https://issues.jboss.org/browse/JBDS-3746 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Environment: Windows 10 Pro > Reporter: Hardy Ferentschik > Labels: havoc > Fix For: 9.1.0.GA > > > On Windows 10 (Pro) after installing and starting the CDK development environment, one is not able to access the OpenShift console (https://10.1.2.2:8443/console) using Microsoft Edge. The IP of the host only network IP does not matter. Using a 192.168 address won't work either. > Using any other browser - IE, Chrome, Firefox - the console can be reached. It seems to be an Edge specific issue and may report the same issue: > * http://www.tenforums.com/installation-setup/8979-dont-forget-edge-can-acc... > * https://social.technet.microsoft.com/Forums/forefront/en-US/0face535-3c7a... > * https://www.google.se/search?q=edge+canot+acess+page&ie=utf-8&oe=utf-8&gw... > I tried several work-arounds, but none worked so far. If there were a confirmed workaround one could image the installer applying it (if possible). In this case we might want to add a warning somewhere in the installer or at least somewhere in the documentation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3615) virtual box cannot be installed reliably on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3615?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3615: -------------------------------- Sprint: (was: devex #6 April 2016) > virtual box cannot be installed reliably on windows > --------------------------------------------------- > > Key: JBDS-3615 > URL: https://issues.jboss.org/browse/JBDS-3615 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: vbox.log > > > look at docker-toolbox what they do that is different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3675) NullPointerException during install (no explanation)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3675?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3675: ----------------------------- > NullPointerException during install (no explanation) > ---------------------------------------------------- > > Key: JBDS-3675 > URL: https://issues.jboss.org/browse/JBDS-3675 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Windows 10 Pro 64bit, Oracle JDK 8_74, installer with EAP > Reporter: Hendy Irawan > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha1 > > Attachments: jboss1.PNG, jboss2.PNG, jbossdev-install-error.PNG > > > Unfortunately no stacktrace whatsoever :( -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3675) NullPointerException during install (no explanation)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3675?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3675: -------------------------------- Target Release: 10.0.0.GA (was: 9.1.0.GA) > NullPointerException during install (no explanation) > ---------------------------------------------------- > > Key: JBDS-3675 > URL: https://issues.jboss.org/browse/JBDS-3675 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Environment: Windows 10 Pro 64bit, Oracle JDK 8_74, installer with EAP > Reporter: Hendy Irawan > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha1 > > Attachments: jboss1.PNG, jboss2.PNG, jbossdev-install-error.PNG > > > Unfortunately no stacktrace whatsoever :( -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3727: ----------------------------- > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3727: -------------------------------- > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3727: -------------------------------- Target Release: 10.0.0.GA > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3721) Installer - Installer should check for required free disk space, ala the JBDS installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3721?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3721: -------------------------------- Fix Version/s: 10.0.0.Alpha1 Target Release: 10.0.0.GA (was: 9.1.0.GA) > Installer - Installer should check for required free disk space, ala the JBDS installer > --------------------------------------------------------------------------------------- > > Key: JBDS-3721 > URL: https://issues.jboss.org/browse/JBDS-3721 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > The current installer is 1.5+GB in size. I have not gotten the installer to run cleanly to a complete installation, but it looks like it requires an additional 4-6 GB. Given that large free space requirement, the installer itself should perform a check and verify that sufficient free space is available before it attempts to perform an install. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3730: -------------------------------- > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432) > at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388) > at com.izforge.izpack.installer.Installer.main(Unknown Source) > [ Automated installation FAILED! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016