[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23373?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-23373:
----------------------------------------
Story Points: 5
Sprint: devex #123 November 2016
Assignee: Dmitrii Bocharov
> Application Wizard: Connection info could be visible on first wizard page
> -------------------------------------------------------------------------
>
> Key: JBIDE-23373
> URL: https://issues.jboss.org/browse/JBIDE-23373
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles.
> We could have it similar as it is in Deploy Docker Image wizard, where we display connection info.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2 as host private network IP not working on (RH) VPN
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21953:
---------------------------------------
Yes, this is the known problem where xip.io does not work from Red Hat offices sometimes (not always). But as far as I'm aware no customer complained about this issue yet.
> 10.1.2.2 as host private network IP not working on (RH) VPN
> -----------------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Critical
> Fix For: LATER
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22201.
---------------------------------
This is definitely no longer happening, so closing.
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM3
>
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19532:
---------------------------------------
I never really had a problem with this, so I am fine this.
> "Edit Server Runtime Environment" Dialog configuration validation is broken
> ---------------------------------------------------------------------------
>
> Key: JBIDE-19532
> URL: https://issues.jboss.org/browse/JBIDE-19532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.4.2.AM3
>
> Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png, JBIDE-19532.png
>
>
> If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start.
> {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist.
> at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84)
> at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227)
> at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months