December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23655) Integration tests: when pulling an image without tag, we should assert that only the latet image is pulled

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23655: ---------------------------------------- Summary: Integration tests: when pulling an image without tag, we should assert that only the latet image is pulled Key: JBIDE-23655 URL: https://issues.jboss.org/browse/JBIDE-23655 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests Affects Versions: 4.4.3.AM1 Reporter: Andre Dietisheim Fix For: 4.4.3.AM2 In https://bugs.eclipse.org/bugs/show_bug.cgi?id=499843 it was discovered that the docker tooling was pulling all images if no tag was provided. We should have a test that asserts that this isnt happening. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-18848. -------------------------------- Verified, I can confirm that: * The ide-config.properties is wraped as maven artifact * ide-config.properties generator (ide-config.properties.py) ** checks for duplicate keys ** checks that there are exactly 8 keys for each prod/version ** checks for presence of ".GA" and ".Final" during stable build > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.Final > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20723) OpenShift 3 application is created even though Cancel button was clicked

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20723?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20723: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > OpenShift 3 application is created even though Cancel button was clicked > ------------------------------------------------------------------------ > > Key: JBIDE-20723 > URL: https://issues.jboss.org/browse/JBIDE-20723 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.4.3.AM2 > > > Once the Finish button in New OpenShift Application wizard is clicked a new application is created no matter what. Even if I click on a Cancel button next to the progress bar of creation process, it looks at first like the process stopped, but it still continues and in few moments a shell with created resources is shown. Can we do something about this? Otherwise cancel button just stop eclipse job and progress bar but it does not do anything more behind it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23321: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.3.AM2 > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23514: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23514 > URL: https://issues.jboss.org/browse/JBIDE-23514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: jmx, openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > Attachments: jmx-error-nodejs.png > > > Most likely server adapters for non-java based apps should not have a jmx node. > Steps to reproduce: > # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template) > # ASSERT: make sure the build is finished, the pod is running. > # ASSERT: make sure that you have a server adapter for your service > # ASSERT: make sure that it is in "[Started, Synchronized]" state) > # EXEC: unfold the server adapter and double click on the JMX child > Result: > An error shows up > !jmx-error-nodejs.png! > {code} > java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278) > at org.jolokia.client.J4pClient.execute(J4pClient.java:191) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23638) Scaling: Sometimes incorrect version of RC leads to error when scaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23638?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23638: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Scaling: Sometimes incorrect version of RC leads to error when scaling > ---------------------------------------------------------------------- > > Key: JBIDE-23638 > URL: https://issues.jboss.org/browse/JBIDE-23638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.3.AM2 > > > Sometimes when scaling an OpenShift 3 application several times, there is an error about failed PUT call. No jobs are running when triggering a scaling. Even though pods are shown correctly (right amount is shown) this error is shown: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/test-project/replicationcontrolle... response code: 409 Operation cannot be fulfilled on replicationcontrollers "nodejs-example-1": the object has been modified; please apply your changes to the latest version and try again > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:155) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23177) Server Editor: Combo items have wrong size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23177?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23177: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Server Editor: Combo items have wrong size > ------------------------------------------ > > Key: JBIDE-23177 > URL: https://issues.jboss.org/browse/JBIDE-23177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Labels: openshift_v3, server_editor > Fix For: 4.4.3.AM2 > > Attachments: combos.png, eclipse-project-overlaps-browse.png > > > When I open an OpenShift 3 Server Editor the combo boxes have weird size, there are overlapping widgets. > !combos.png! > Spotted on Fedora 24 with GTK 3. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016