March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19522) Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info .

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19522?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19522. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Snapshot wizard: Snapshot restore app from different type archive does not pop up with failure info . > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-19522 > URL: https://issues.jboss.org/browse/JBIDE-19522 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.CR1 > Environment: JBoss Developer Studio 8.1.0 Beta1 > Reporter: Yanping Zhang > Assignee: Andre Dietisheim > Labels: openshift_v2, snapshot_wizard > Fix For: 4.5.3.Final > > > [~yanpzhan] if you get the info in the console that the snapshot could be restored (the server is reporting in the console, not the tooling), so I would think that this is a bug in the server? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22743. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > SSH keys are not fetched by default > ----------------------------------- > > Key: JBIDE-22743 > URL: https://issues.jboss.org/browse/JBIDE-22743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v2, sshkeys_wizard > Fix For: 4.5.3.Final > > > In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19971. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v2 > Fix For: 4.5.3.Final > > Attachments: authorized.png, creds_prompt.png, jstack.txt, krb5-auth-method-is-1st.png > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) the importing job in IDE is hanging. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21792) Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21792?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21792. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Server Adapter Wizard: OpenShift 2 domains are not ordered alphanumerically > --------------------------------------------------------------------------- > > Key: JBIDE-21792 > URL: https://issues.jboss.org/browse/JBIDE-21792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, server_adapter_wizard > Fix For: 4.5.3.Final > > > Domains listed in a combo in the New OpenShift 2 Server Adapter wizard are currently not order alphabetically or alphanumerically. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12118) Port forwarding: more specific auth error description

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12118. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Port forwarding: more specific auth error description > ----------------------------------------------------- > > Key: JBIDE-12118 > URL: https://issues.jboss.org/browse/JBIDE-12118 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, port_forwarding_wizard > Fix For: 4.5.3.Final > > Attachments: port.png, tail.png > > > Provide a uniform message in the Error dialogs like in JBIDE-11810, saying that user probably doesn't have ssh key listed in preferences. > Current state: > * Port forwarding, environment variables > !port.png|thumbnail! > * Tail files > !tail.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18038) Server adapter: Switching between workspace without and with OpenShift server adapter cause invoking connection dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18038?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-18038. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Server adapter: Switching between workspace without and with OpenShift server adapter cause invoking connection dialog > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18038 > URL: https://issues.jboss.org/browse/JBIDE-18038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > Switching from workspace without OpenShift server adapter to workspace with opened details for OpenShift server adapter opens connection dialog (credentials) before opening workbench. After canceling/completing this connection dialog, workbench shell is opened. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20126) v2 Import-, application wizard: use easy import, not our custom facility

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20126?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20126. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > v2 Import-, application wizard: use easy import, not our custom facility > ------------------------------------------------------------------------ > > Key: JBIDE-20126 > URL: https://issues.jboss.org/browse/JBIDE-20126 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > > The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20636) Push changes: Management interface wont come up while deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20636?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20636. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Push changes: Management interface wont come up while deployment > ---------------------------------------------------------------- > > Key: JBIDE-20636 > URL: https://issues.jboss.org/browse/JBIDE-20636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > > Reference: https://github.com/openshift/origin/issues/4502 > {code} > Preparing build for deployment > Deployment id is f2c69660 > Activating deployment > Starting PHPMyAdmin cartridge > Starting MySQL 5.5 cartridge Deploying JBoss > Starting jbossas cartridge > Found 127.3.158.129:8080 listening port > Found 127.3.158.129:9999 listening port > CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification > ------------------------- > Git Post-Receive Result: success > Activation status: success > Deployment completed with status: success > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10788) Server Adapter: Add setting ui for openshift source servers to use wtp context root if required

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10788?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10788. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > Server Adapter: Add setting ui for openshift source servers to use wtp context root if required > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-10788 > URL: https://issues.jboss.org/browse/JBIDE-10788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 3.3.0.M5 > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v2, server_adapter > Fix For: 4.5.3.Final > > > link to JBIDE-10514 , a UI is required for this setting. > 1. Create a new application in wizard and allow to create a new project in the workspace > 2. Fix all the bugs so that it compiles (delete modules.jsp, add java version 1.6 to pom.xml, reload project configuration) > 3. Modify all your build stuff so the project does NOT deploy to root > 4. Change your context root to match what your setting is in the build > 5. Right click the project and select Run as... + Run on server > 6. Choose associated openshift server > 7. Result - No page found due to the incorrect URL. It's still using root instead of your new custom context root > A UI is required for this setting -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 resolved JBIDE-19851. -------------------------------------- Resolution: Won't Fix resolving all OpenShift 2 issues since support for OpenShift faded out. > 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 > Assignee: Andre Dietisheim > Labels: environment_variables, openshift_v2 > Fix For: 4.5.3.Final > > > 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 (v7.5.0#75005)

8 years, 3 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 March 2018