July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12098?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12098: ------------------------------------------ I did not run across this for quite some time now. I now tried once more and still did not run across it. I'll thus close this as outdated. We can still re-open if this happens again. > OpenShift Explorer: Timeout exception when forcing domain deletion > ------------------------------------------------------------------ > > Key: JBIDE-12098 > URL: https://issues.jboss.org/browse/JBIDE-12098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: deletedomain.png > > > Tried to force domain deletion while having (medium geared) application on OpenShift. > Screenshot: > !deletedomain.png|thumbnail! > Stack trace: > {code} > com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out > at com.openshift.internal.client.RestService.request(RestService.java:109) > at com.openshift.internal.client.RestService.request(RestService.java:89) > at com.openshift.internal.client.RestService.request(RestService.java:74) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137) > at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329) > at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166) > at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12098?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12098. -------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) Resolution: Out of Date > OpenShift Explorer: Timeout exception when forcing domain deletion > ------------------------------------------------------------------ > > Key: JBIDE-12098 > URL: https://issues.jboss.org/browse/JBIDE-12098 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: deletedomain.png > > > Tried to force domain deletion while having (medium geared) application on OpenShift. > Screenshot: > !deletedomain.png|thumbnail! > Stack trace: > {code} > com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out > at com.openshift.internal.client.RestService.request(RestService.java:109) > at com.openshift.internal.client.RestService.request(RestService.java:89) > at com.openshift.internal.client.RestService.request(RestService.java:74) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137) > at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329) > at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166) > at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2425: ----------------------------------- What is the distinction between Tested and External? Tested are hosted by us? We should indicate that fact. Experimental should not say "Tested by Red Hat". Simply say "These are experimental plugins..." > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.x, 8.0.x, 7.1.x > > Attachments: 2425.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12118?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12118: ------------------------------------------ I am not sure that having an uniformous error message really is what we want. There are many other reasons for SSH failures, not just keys that are not listed. You can cancel the passphrase dialog when you're prompted, you can have invalid keys and you can also have keys that are removed from OpenShift. IMHO there's nothing but some wording that can get improved but we tell the user what operation he triggered went wrong unveiling the internal details in the details only. WDYT? > OpenShift: 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: Xavier Coulon > Priority: Minor > Fix For: 4.2.x > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12164) Port-forwarding dialog does not detect when SSH session stops

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12164?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-12164: --------------------------------------- I guess so.. Maybe you could set the timeout value to a lower value to avoid too long waiting periods (just my 2c$ here) > Port-forwarding dialog does not detect when SSH session stops > ------------------------------------------------------------- > > Key: JBIDE-12164 > URL: https://issues.jboss.org/browse/JBIDE-12164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > > During some demo preparation, the SSH session used to enable port-forwarding was closed, but the dialog kept reporting that port-forwarding was still enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12164) Port-forwarding dialog does not detect when SSH session stops

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12164?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12164: ------------------------------------------ [~xcoulon] Xavier, I guess that there's no other way to simulate this but to let ssh-session expire while the dialog is opened? > Port-forwarding dialog does not detect when SSH session stops > ------------------------------------------------------------- > > Key: JBIDE-12164 > URL: https://issues.jboss.org/browse/JBIDE-12164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > > During some demo preparation, the SSH session used to enable port-forwarding was closed, but the dialog kept reporting that port-forwarding was still enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12306) OpenShift wizard remebers filled app info even though I'm using a different user

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12306?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12306. -------------------------------------- Resolution: Out of Date This does not happen any more in the current implementation (4.2.0.Alpha1). Once you get back to the credentials page and return to the applications page, all the settings are resetted. Especially the name of the existing application is blanked thus the error described in the description wont appear. > OpenShift wizard remebers filled app info even though I'm using a different user > -------------------------------------------------------------------------------- > > Key: JBIDE-12306 > URL: https://issues.jboss.org/browse/JBIDE-12306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.Alpha1, 4.0.0.Alpha1 > > Attachments: JBIDE-11310.patch, JBIDE12306.patch, prefilled.png > > > The wizard model probably doesn't refresh/reset... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12306) OpenShift wizard remebers filled app info even though I'm using a different user

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12306: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > OpenShift wizard remebers filled app info even though I'm using a different user > -------------------------------------------------------------------------------- > > Key: JBIDE-12306 > URL: https://issues.jboss.org/browse/JBIDE-12306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.0.0.Alpha1, 4.2.0.Alpha1 > > Attachments: JBIDE-11310.patch, JBIDE12306.patch, prefilled.png > > > The wizard model probably doesn't refresh/reset... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- xiaoli <xtian(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] Move it back to ON_QA according to comment 7 and comment 9 > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- xiaoli <xtian(a)redhat.com> changed the Status of [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] from ASSIGNED to ON_QA > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 July 2013