December 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-998) Fuse - Adapt 'RouteManipulationTest' according to FUSETOOLS-2023

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-998?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-998. ----------------------------------- pushed to master > Fuse - Adapt 'RouteManipulationTest' according to FUSETOOLS-2023 > ----------------------------------------------------------------- > > Key: JBTIS-998 > URL: https://issues.jboss.org/browse/JBTIS-998 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.0.Final > > Original Estimate: 1 hour > Time Spent: 1 hour > Remaining Estimate: 0 minutes > > Changes introduced with https://issues.jboss.org/browse/FUSETOOLS-2023 broke the _RouteManipulationTest_. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23639) Application wizard: Templates parameters show wrong values if using existing eclipse project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23639?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23639: ------------------------------------- Fix Version/s: 4.4.3.AM1 > Application wizard: Templates parameters show wrong values if using existing eclipse project > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23639 > URL: https://issues.jboss.org/browse/JBIDE-23639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new OpenShift 3 application based on an eclipse project from workspace using a template, template parameters shows wrong values. E.g. I am having a project with git repo URL URL_A and template is based on source code from git repo URL URL_B. In the wizard, if I select at first template and then eclipse project, the template parameters values on the next wizard page shows values of the template instead of eclipse project. But correct values are shown. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 edited comment on JBIDE-23638 at 12/13/16 6:30 AM: -------------------------------------------------------------------- This looks like a refresh problem in our cache. [~mlabuda] Refreshing helps to get the scaling work again, doesnt it? was (Author: adietish): This looks like a refresh problem in our cache. > 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.AM1 > > > 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)

9 years, 3 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.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.AM1 > > > 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)

9 years, 3 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 commented on JBIDE-23638: ------------------------------------------ This looks like a refresh problem in our cache. > 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.AM1 > > > 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23641: ------------------------------------ Tested on Win10, works without problem > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: fede pia > Priority: Blocker > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23633) Integration tests: suite (ex. BuildImageTest) should build a much smaller image to speed up the whole suite

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23633?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23633: ------------------------------------- Summary: Integration tests: suite (ex. BuildImageTest) should build a much smaller image to speed up the whole suite (was: Integration tests: BuildImageTest should build a much smaller image to speed up the whole suite) > Integration tests: suite (ex. BuildImageTest) should build a much smaller image to speed up the whole suite > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23633 > URL: https://issues.jboss.org/browse/JBIDE-23633 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-999) Add Consume SOAP Digest test + update Consume REST/SOAP tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-999?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-999. ------------------------------ PR was pushed to master branch > Add Consume SOAP Digest test + update Consume REST/SOAP tests > ------------------------------------------------------------- > > Key: JBTIS-999 > URL: https://issues.jboss.org/browse/JBTIS-999 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.4.0.Final, 4.3.3.Final > Reporter: stanislav kaleta > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final, 4.3.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23285: --------------------------------------- Initial shot at the unification: https://github.com/jbosstools/jbosstools-integration-tests/pull/1704 > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.3.AM1 > > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23285: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1625, https://github.com/jbosstools/jbosstools-integration-tests/pull/1704 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1625) > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.3.AM1 > > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016