[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Description:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
This is happening only some times. I have created EAP application where this is happening.
was:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
> This is happening only some times. I have created EAP application where this is happening.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Labels: environment_variables (was: )
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable for a OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Description:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
was:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
> Cannot refresh environment variable for a OpenShift application
> ---------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Summary: Cannot refresh environment variable(s) for an OpenShift application (was: Cannot refresh environment variable for a OpenShift application)
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable for a OpenShift application
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-19851:
-------------------------------------
Summary: Cannot refresh environment variable for a OpenShift application
Key: JBIDE-19851
URL: https://issues.jboss.org/browse/JBIDE-19851
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
[~maxandersen] What you're asking is currently not possible, since the target are mostly hardcoded inside the publish.sh scripts. However, there's indeed a room for improvement there. But I believe it'd be better to track it in a separate Jira.
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
What is the easiest way for me to test this on Mac and try have it publish to my own locations instead of download.jboss.org ?
I would like to avoid me running mvn deploy modifies already deployed content I didn't expect ;)
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19839) Cannot proceed to New OpenShift Application wizard via shell menu
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-19839:
---------------------------------------
Ah, sorry for omiting significant info about required perspective. This is available in JBoss perspective.
> Cannot proceed to New OpenShift Application wizard via shell menu
> -----------------------------------------------------------------
>
> Key: JBIDE-19839
> URL: https://issues.jboss.org/browse/JBIDE-19839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png
>
>
> While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed).
> Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19839) Cannot proceed to New OpenShift Application wizard via shell menu
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19839:
----------------------------------
Steps to Reproduce:
ASSERT: JBoss perspective is active.
(OPTIONAL - does not have effect on result: Have a connection in OpenShift explorer view. If there is no connection, New connection is preselected in connection dialog before opening New OpenShift Application wizard)
EXEC: Open New OpenShift Application wizard via shell menu File -> New -> OpenShift Application
ASSERT: Connection dialog is opened.
ASSERT: Finish button is disabled.
EXEC: Fill in credentials.
RESULT: Finish button is still disabled.
EXPECTED RESULT: Finish button is enabled.
was:
(OPTIONAL - does not have effect on result: Have a connection in OpenShift explorer view. If there is no connection, New connection is preselected in connection dialog before opening New OpenShift Application wizard)
EXEC: Open New OpenShift Application wizard via shell menu File -> New -> OpenShift Application
ASSERT: Connection dialog is opened.
ASSERT: Finish button is disabled.
EXEC: Fill in credentials.
RESULT: Finish button is still disabled.
EXPECTED RESULT: Finish button is enabled.
> Cannot proceed to New OpenShift Application wizard via shell menu
> -----------------------------------------------------------------
>
> Key: JBIDE-19839
> URL: https://issues.jboss.org/browse/JBIDE-19839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png
>
>
> While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed).
> Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19839) Cannot proceed to New OpenShift Application wizard via shell menu
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19839?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19839:
------------------------------------------
[~mlabuda] I dont get what you are referring to, I dont see an item File->New->OpenShift Application,
!file-new-no_openshift.png!
I only see an openshift entry in File->New->Other->OpenShift->New OpenShift Application"
!file-new-other-openshift.png!
> Cannot proceed to New OpenShift Application wizard via shell menu
> -----------------------------------------------------------------
>
> Key: JBIDE-19839
> URL: https://issues.jboss.org/browse/JBIDE-19839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
> Attachments: file-new-no_openshift.png, file-new-other-openshift.png, new-application-wizard-via-file-new.png
>
>
> While trying to open a New OpenShift Application wizard via shell menu (File -> New -> OpenShift Application) it is not possible to get behind connection dialog. At first connection dialog is opened to chose desired connection where to create a new OpenShift application. After filling details and hitting the Finish button, New OpenShift Application should be opened. Issue is that it is not possible to click Finish button at all, because it is disabled all the time (grayed).
> Same thing is in Central. Opening New OpenShift Application wizard via hyperlink in Central blocks user to proceed through connection dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months