June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19584) Explorer: error child (could not connect) to v3 connection has "New" context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19584?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19584: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Explorer: error child (could not connect) to v3 connection has "New" context menu > --------------------------------------------------------------------------------- > > Key: JBIDE-19584 > URL: https://issues.jboss.org/browse/JBIDE-19584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: new-context-menu-for-exception.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19851: ------------------------------------- Labels: environment_variables openshift_v2 (was: environment_variables) > 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 > Priority: Minor > Labels: environment_variables, openshift_v2 > Fix For: 4.3.0.Beta2 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19851: ------------------------------------------ [~mlabuda] do you know a workaround for this? How does it behave if you close the view and request again? > 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 > Priority: Minor > Labels: environment_variables > Fix For: 4.3.0.Beta2 > > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19506: ------------------------------------------ Very much wanted but not crucial enough to be forced to 4.3.0.Beta2 given the limited time there is to do it. > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.x > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19412: ------------------------------------------ Cleanup task, moving to 4.3.x > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.x > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.x > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19759: ------------------------------------- Description: If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central. was:If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. > This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19412) Cleanup ConnectionURL usage for v3 connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19412: ------------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > Cleanup ConnectionURL usage for v3 connections > ---------------------------------------------- > > Key: JBIDE-19412 > URL: https://issues.jboss.org/browse/JBIDE-19412 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.x > > > In ConnectionsRegistry connections are stored by ConnectionURL. ConnectionURL is also used to persist v2 connections. v3 connections on the other hand are persisted in their very own json format. We need to clean this discrepany/inconsistency. We should either only use ConnectionURL for v2 connections or also store v3 connections in the ConnectionURL format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19817: ------------------------------------------ This is crucial to be able to provide JBDIE-19759. JBIDE-19759 is what a newbie user will come across when hitting "New OpenShift Application" from central. > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20004: ------------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > OpenShift v3 resources names should be camelcasized or splitted by space character > ---------------------------------------------------------------------------------- > > Key: JBIDE-20004 > URL: https://issues.jboss.org/browse/JBIDE-20004 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.CR1 > > > Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. > Affected resources: > * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" > * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" > * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" > * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" > I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015