[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23352:
----------------------------------
Assignee: Jeff MAURY
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23352:
-------------------------------
Story Points: 12
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23352:
-------------------------------
Sprint: devex #123 November 2016
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4156) Skip detected components in cdk's createEnvironment
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4156?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4156.
-----------------------------
Verified in B217.
> Skip detected components in cdk's createEnvironment
> ---------------------------------------------------
>
> Key: JBDS-4156
> URL: https://issues.jboss.org/browse/JBDS-4156
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.2.0.AM3
>
>
> When installing cdk using detected components, the locations stored to the environment are empty (""/bin to be precise). In the end it generates this log entry:
> {noformat}Thu, 03 Nov 2016 11:46:04 GMT-INFO: cdk - Set PATH environment variable to 'undefined;bin;bin;'{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-21812) Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21812?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21812:
---------------------------------------
Unfortunately I am not able to reproduce this.
First I tried with devstudio 10.2.0.AM3 (Eclipse Neon + JBoss Tools 4.4.2.AM3) and then devstudio 9.1 (Eclipse Mars + JBoss Tools 4.3).
This is what I did:
1. Start devstudio
2. Create a jboss as 7.1.1 server, make sure you use oracle java 1.7 and management profile
3. Start / stop server several times, expand some nodes in the server view - Server Details, go deeper...
But I still did not see any error in the workspace log.
> Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1
> ----------------------------------------------------------------------
>
> Key: JBIDE-21812
> URL: https://issues.jboss.org/browse/JBIDE-21812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final, 4.3.1.Beta2
> Environment: JBoss AS 7.1.1
> Eclipse Mars.2 4.5.2
> IPv4 stack specified
> Local host connectivity (127.0.0.1 specified)
> Reporter: William Darby
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
> Attachments: eclipse.log
>
>
> When starting JBoss from within Eclipse the following error appears on the console:
> 17:25:23,182 ERROR [org.jboss.remoting.remote.connection] (Remoting "hostname:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine
> This occurs with or without firewall/anti-virus enabled.
> And with the startup/shutdown pollers set to Management Service or Web Port.
> Also with Server Ports specified or 'Detected from Local Runtime'
> It occurs occasionally on the first server startup, but repeatedly after stopping and restarting the server.
> It also occurs when the 'Server Details' are browsed in the Servers view, i.e., selecting any folder will cause another of the errors to display.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23471:
---------------------------------------
After quitting devstudio and launching again, I can no longer reproduce - central loaded as expected.
So unless somebody else is somehow able to reproduce this, I guess there's not much that can be done here.
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> !central-error.png!
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23471:
----------------------------------
Description:
I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
{code}
Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
/Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
{code}
!central-error.png!
JBoss Central page could not be loaded.
Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
[1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
was:
I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
{code}
Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
/Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
{code}
JBoss Central page could not be loaded.
Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
[1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> !central-error.png!
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23471:
----------------------------------
Attachment: central-error.png
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
Martin Malina created JBIDE-23471:
-------------------------------------
Summary: Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
Key: JBIDE-23471
URL: https://issues.jboss.org/browse/JBIDE-23471
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.4.2.AM3
Reporter: Martin Malina
I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
{code}
Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
/Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
{code}
JBoss Central page could not be loaded.
Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
[1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months