October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22803 at 10/6/16 5:55 AM: ------------------------------------------------------------------- [~dbocharov] Maybe we can take the repeated, delay- and endless erroring (that you reported above, the repeated calling of the error callback/listener) and deduce from it that watching projects wont work? The above finding that onFailure is called repeatedly, endlessly, in a manner without significant delays looks like such a way, but yes I agree that it would be a hack, since the response we see in #onFailure is "OK" (message). But it looks to me as if using this "hack" while properly identifying it as such (javadoc, comment, methodname, etc.) still makes it a viable solution? was (Author: adietish): [~dbocharov] Maybe we can take the repeated, delay- and endless erroring (that you reported above, the repeated calling of the error callback/listener) and deduce from it that watching projects wont work? > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22803: ------------------------------------------ In your finding above you report {quote} onFailure(IOException, Response) then we'll see the following: Response {protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} {quote} This looks like a bug to me that we should report, correct? > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22803 at 10/6/16 5:46 AM: ------------------------------------------------------------------- In your finding above you report {code} onFailure(IOException, Response) then we'll see the following: Response {protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} {code} This looks like a bug to me that we should report, correct? was (Author: adietish): In your finding above you report {quote} onFailure(IOException, Response) then we'll see the following: Response {protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} {quote} This looks like a bug to me that we should report, correct? > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22803: ------------------------------------------ [~dbocharov] Maybe we can take the repeated, delay- and endless erroring (that you reported above, the repeated calling of the error callback/listener) and deduce from it that watching projects wont work? > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23182: ------------------------------------------ [~scabanovich] this somehow rings my bell in that I know that there are very weird things happening with the selection in the properties view. I couldnt confirm nor refute your finding though, , I assume it definitely is. Given your finding is correct and your approach fixes it it's a workaround. We should therefore comment this in the code and file an issue in Eclipse? > NullPointerException in PodLogsHandler.handleEvent > -------------------------------------------------- > > Key: JBIDE-23182 > URL: https://issues.jboss.org/browse/JBIDE-23182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Labels: openshift_v3, pod_log_console > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46) > at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22803: ------------------------------------------ [~bdshadow] If I understand things right then in 3.2 one has to be admin to be able to retrieve the version while in 3.3 a normal user can, correct? > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22803: ------------------------------------- Summary: Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values (was: When OS projects are created and deleted, seems Openshift explorer restores non existing values) > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23267) New application created by JBDS cannot specify "medium" or "large" size.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23267?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23267. --------------------------------- Verified in DevStudio 10.2.0.AM2 build ID AM2-v20161005-2259-B6159. > New application created by JBDS cannot specify "medium" or "large" size. > ------------------------------------------------------------------------ > > Key: JBIDE-23267 > URL: https://issues.jboss.org/browse/JBIDE-23267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: * All versions > * I confirmed with latest version devstudio-10.0.0.GA-installer-standalone.jar > Reporter: Kenjiro Nakayama > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, gear, openshift_v2 > Fix For: 4.4.2.AM2 > > Original Estimate: 4 hours > Time Spent: 1 hour > Remaining Estimate: 3 hours > > * New application created by JBDS cannot specify "medium" or "large" size. > * NOTE: This issue is critical if the users environment doesn't allow to create small gears. Since they cannot create any application via JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4094) After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4094?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4094: ---------------------------------- Workaround Description: in edit connection, switch to basic authentication and use openshift-devel/devel authentication > After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4094 > URL: https://issues.jboss.org/browse/JBDS-4094 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift, platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Alexey Kazakov > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4094) After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4094: ------------------------------------- Summary: After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance Key: JBDS-4094 URL: https://issues.jboss.org/browse/JBDS-4094 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: openshift, platform-installer Affects Versions: 10.1.0.GA Reporter: Aurélien Pupier Assignee: Alexey Kazakov -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 October 2016