October 2016 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------- Description: 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! was: 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 > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > > 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.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_latest, scaling_pods_wizard > 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 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23415) use Import-Package instead of Require-Bundle for slf4j.api [livereload]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23415?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23415: ------------------------------------ We don't ship tests in devstudio so this is not a blocker. But we should move to from require-bundle to import-package anyway, as that's the recommended approach. > use Import-Package instead of Require-Bundle for slf4j.api [livereload] > ----------------------------------------------------------------------- > > Key: JBIDE-23415 > URL: https://issues.jboss.org/browse/JBIDE-23415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.2.AM3 > > > Because livereload tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-livereload/blob/44af911aba916f0e... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23415) use Import-Package instead of Require-Bundle for slf4j.api [livereload]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23415?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23415: ------------------------------- Priority: Minor (was: Blocker) > use Import-Package instead of Require-Bundle for slf4j.api [livereload] > ----------------------------------------------------------------------- > > Key: JBIDE-23415 > URL: https://issues.jboss.org/browse/JBIDE-23415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because livereload tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-livereload/blob/44af911aba916f0e... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23414) use Import-Package instead of Require-Bundle for slf4j.api [central]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23414?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23414: ------------------------------------ We don't ship maven.gwt in devstudio is this is not a blocker. The plugin is deprecated and should just be removed, as we dropped gwt support YEARS ago. > use Import-Package instead of Require-Bundle for slf4j.api [central] > -------------------------------------------------------------------- > > Key: JBIDE-23414 > URL: https://issues.jboss.org/browse/JBIDE-23414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23414) use Import-Package instead of Require-Bundle for slf4j.api [central]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23414?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23414: ------------------------------- Priority: Minor (was: Blocker) > use Import-Package instead of Require-Bundle for slf4j.api [central] > -------------------------------------------------------------------- > > Key: JBIDE-23414 > URL: https://issues.jboss.org/browse/JBIDE-23414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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 commented on JBIDE-23030: ------------------------------------------ I believe that this is very closely related or even the same as JBIDE-23412 > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > > 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 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23415) use Import-Package instead of Require-Bundle for slf4j.api [livereload]

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-23415: -------------------------------------- Summary: use Import-Package instead of Require-Bundle for slf4j.api [livereload] Key: JBIDE-23415 URL: https://issues.jboss.org/browse/JBIDE-23415 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate, rpm Affects Versions: 4.4.2.AM2 Reporter: Nick Boldt Assignee: Koen Aers Priority: Blocker Fix For: 4.4.2.AM3 Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. Here's the line that is causing the problem: https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. More info in JBDS-4136 See also: http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23415) use Import-Package instead of Require-Bundle for slf4j.api [livereload]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23415?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23415: -------------------------------------- Component/s: livereload (was: hibernate) Description: Because livereload tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. Here's the line that is causing the problem: https://github.com/jbosstools/jbosstools-livereload/blob/44af911aba916f0e... We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. More info in JBDS-4136 See also: http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... was: Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. Here's the line that is causing the problem: https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. More info in JBDS-4136 See also: http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... Assignee: Xavier Coulon (was: Koen Aers) > use Import-Package instead of Require-Bundle for slf4j.api [livereload] > ----------------------------------------------------------------------- > > Key: JBIDE-23415 > URL: https://issues.jboss.org/browse/JBIDE-23415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.2.AM3 > > > Because livereload tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-livereload/blob/44af911aba916f0e... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23414) use Import-Package instead of Require-Bundle for slf4j.api [central]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23414?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23414: -------------------------------------- Component/s: central (was: hibernate) Description: Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. Here's the line that is causing the problem: https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. More info in JBDS-4136 See also: http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... was: Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. Here's the line that is causing the problem: https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. More info in JBDS-4136 See also: http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... Assignee: Fred Bricon (was: Koen Aers) > use Import-Package instead of Require-Bundle for slf4j.api [central] > -------------------------------------------------------------------- > > Key: JBIDE-23414 > URL: https://issues.jboss.org/browse/JBIDE-23414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.2.AM3 > > > Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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 October 2016