November 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-975) SY - Avoid waiting for the 'Synchronizing EMF resources'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-975?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-975: ----------------------------------------- If there are some jobs still running and you try to promote a service then the job 'Synchronizing EMF resources' is still running while the dialog is open. Note that you can press 'Cancel' or 'Finish' without any problem and then the job stops. > SY - Avoid waiting for the 'Synchronizing EMF resources' > -------------------------------------------------------- > > Key: JBTIS-975 > URL: https://issues.jboss.org/browse/JBTIS-975 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > > Sometimes It happens that some jobs take more than one minute and that's why my tests fail > {code} > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running > Refreshing SwitchYard project configuration. > Synchronizing EMF resources > Updating Maven Project > {code} > Usually the test 'SwitchYardIntegrationDroolsTest' fails due to the above exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-975) SY - Avoid waiting for the 'Synchronizing EMF resources'

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-975: --------------------------------------- Summary: SY - Avoid waiting for the 'Synchronizing EMF resources' Key: JBTIS-975 URL: https://issues.jboss.org/browse/JBTIS-975 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE, switchyard Affects Versions: 4.4.0.Alpha1 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.4.0.Final Sometimes It happens that some jobs take more than one minute and that's why my tests fail {code} org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running Refreshing SwitchYard project configuration. Synchronizing EMF resources Updating Maven Project {code} Usually the test 'SwitchYardIntegrationDroolsTest' fails due to the above exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23030: ------------------------------------- Attachment: replicas-0.png > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23030: ------------------------------------- Attachment: rc-1-replicas-0.png > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23030: ------------------------------------- Attachment: rc2-replicas-1.png > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-23213: ----------------------------------- [~mmalina], we can update it pretty much up to the GA date before we release the docs. cc: [~supriya.bharadwaj] > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23184: ------------------------------------------ [~dbocharov] I merged your patch for openshift-restclient-java into master. I also deployed the new client lib to repository.jboss.org. I'd love you to test the new artifact a bit (if it fixes this and works in general) and confirm this. This would allow us to release a 5.2.0.Final before freezing tomorrow. > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23418: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23418: ---------------------------------------- Assignee: Viacheslav Kabanovich > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23418: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016