January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6080) Management console - cluster view page displays offline nodes from other clusters

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6080?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-6080: --------------------------------- Assignee: Vladimir Blagojevic > Management console - cluster view page displays offline nodes from other clusters > --------------------------------------------------------------------------------- > > Key: ISPN-6080 > URL: https://issues.jboss.org/browse/ISPN-6080 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Go to Clusters -> Make sure one cluster is stopped, the other is started -> go to started cluster > Result: Nodes from started cluster are displayed as well as nodes from stopped cluster. > Expected result: Only nodes from started cluster should be displayed in "started" cluster page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6075) Created cache appears as available in UI

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6075?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-6075: -------------------------------- Summary: Created cache appears as available in UI (was: Created cache is immediately available) > Created cache appears as available in UI > ---------------------------------------- > > Key: ISPN-6075 > URL: https://issues.jboss.org/browse/ISPN-6075 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Martin Gencur > > Steps to reproduce: > 1) Add new cache > 2) Go to the cache detail page > Issues: > 1) The label in top-left corner says "Available" while it should be either Unavailable or Disabled at this point (probably it is because this page still shows the satus of the currentCluster and not the cache itself) > 2) The actions on the right side include both "Disable" and "Enable" and both of them are clickable. Only "Enable" option should be available at this point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6054) Docker image cannot build website

by Emmanuel Bernard (JIRA)

[ https://issues.jboss.org/browse/ISPN-6054?page=com.atlassian.jira.plugin.... ] Emmanuel Bernard commented on ISPN-6054: ---------------------------------------- Adding [~NadirX] as he is usually the one updating the Gemfile for the lot. > Docker image cannot build website > --------------------------------- > > Key: ISPN-6054 > URL: https://issues.jboss.org/browse/ISPN-6054 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Reporter: Emmanuel Bernard > > There are several issues with the Docker image: > 1. it uses Ruby 2.2 which apparently make Awestruct 0.5.7.RC2 + Guard fail > 2. the Gemfile.lock conflicts > For 1. the error is as followed https://gist.github.com/emmanuelbernard/0524a56f2f859569c634 > The best is for Awestruct to fix the issue (assuming the analysis is correct). The alternative is to install rvm inside the docker image to controll the ruby version used. It requires a few experimentations (probably 2 to 4 hours of work) > For 2. the problem is as followed: > - docker build installs and create a Gemfile.lock with specific versions > - the host might already have a Gemfile.lock or worse, does not have one > - when running docker, we do bind the host directory on top of the docker directory > - so the host Gemfile.lock is used (different from Docker's gemfile.lock) and this will look for potentially incorrect dependencies and fail > The solutions to 2 are: > - create a build_docker.sh which will build the docker image, remove Gemfile.lock from the host and rerun the rake setup step to rebuild the Gemfile.lock to the right value ; since the host dir will be mapped, the Gemfile.lock will survive a docker image restart > - change the scripts to store the Gemfile.lock somewhere in a non mapped directory of the docker image and use an environment variable set in Dockerfile to influence our Rakefile (we do that already with the env variable BIND) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6054) Docker image cannot build website

by Emmanuel Bernard (JIRA)

[ https://issues.jboss.org/browse/ISPN-6054?page=com.atlassian.jira.plugin.... ] Emmanuel Bernard commented on ISPN-6054: ---------------------------------------- [~hardy.ferentschik] pointed out that the issue number 2 would not have happened if the Gemfile.lock was committed to git. It appears to be a best practice in the Gem community (for "end applications" at least). So we should commit that file in Git and also make sure that whoever updates this Gemfile.lock also makes sure the docker image is functional by rebuilding it. > Docker image cannot build website > --------------------------------- > > Key: ISPN-6054 > URL: https://issues.jboss.org/browse/ISPN-6054 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Reporter: Emmanuel Bernard > > There are several issues with the Docker image: > 1. it uses Ruby 2.2 which apparently make Awestruct 0.5.7.RC2 + Guard fail > 2. the Gemfile.lock conflicts > For 1. the error is as followed https://gist.github.com/emmanuelbernard/0524a56f2f859569c634 > The best is for Awestruct to fix the issue (assuming the analysis is correct). The alternative is to install rvm inside the docker image to controll the ruby version used. It requires a few experimentations (probably 2 to 4 hours of work) > For 2. the problem is as followed: > - docker build installs and create a Gemfile.lock with specific versions > - the host might already have a Gemfile.lock or worse, does not have one > - when running docker, we do bind the host directory on top of the docker directory > - so the host Gemfile.lock is used (different from Docker's gemfile.lock) and this will look for potentially incorrect dependencies and fail > The solutions to 2 are: > - create a build_docker.sh which will build the docker image, remove Gemfile.lock from the host and rerun the rake setup step to rebuild the Gemfile.lock to the right value ; since the host dir will be mapped, the Gemfile.lock will survive a docker image restart > - change the scripts to store the Gemfile.lock somewhere in a non mapped directory of the docker image and use an environment variable set in Dockerfile to influence our Rakefile (we do that already with the env variable BIND) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6081) Creating new cache with name that already exists leads to no response in the UI

by Martin Gencur (JIRA)

Martin Gencur created ISPN-6081: ----------------------------------- Summary: Creating new cache with name that already exists leads to no response in the UI Key: ISPN-6081 URL: https://issues.jboss.org/browse/ISPN-6081 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 8.1.0.Final Reporter: Martin Gencur Priority: Minor Steps to reproduce: Cache container detail page -> Add Cache -> fill in cache name and base configuration -> click Next -> click Create -> click Create on the following screen again Result: There's an error in the server log but the console does not show any warning. The modal dialog stays open and users don't not know what happened unless they look at server logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6080) Management console - cluster view page displays offline nodes from other clusters

by Roman Macor (JIRA)

Roman Macor created ISPN-6080: --------------------------------- Summary: Management console - cluster view page displays offline nodes from other clusters Key: ISPN-6080 URL: https://issues.jboss.org/browse/ISPN-6080 Project: Infinispan Issue Type: Bug Components: Console Reporter: Roman Macor Steps to reproduce: Go to Clusters -> Make sure one cluster is stopped, the other is started -> go to started cluster Result: Nodes from started cluster are displayed as well as nodes from stopped cluster. Expected result: Only nodes from started cluster should be displayed in "started" cluster page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes in management console by IP doesn't work

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6079?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-6079: ------------------------------ Summary: Searching nodes in management console by IP doesn't work (was: Searching nodes by IP doesn't work) > Searching nodes in management console by IP doesn't work > -------------------------------------------------------- > > Key: ISPN-6079 > URL: https://issues.jboss.org/browse/ISPN-6079 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > > Searching nodes by IP address doesn't work. e.g. 127.0.0.1 > Result: No nodes are matched. > Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes in management console by IP address doesn't work

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6079?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-6079: ------------------------------ Summary: Searching nodes in management console by IP address doesn't work (was: Searching nodes in management console by IP doesn't work) > Searching nodes in management console by IP address doesn't work > ---------------------------------------------------------------- > > Key: ISPN-6079 > URL: https://issues.jboss.org/browse/ISPN-6079 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > > Searching nodes by IP address doesn't work. e.g. 127.0.0.1 > Result: No nodes are matched. > Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6079) Searching nodes by IP doesn't work

by Roman Macor (JIRA)

Roman Macor created ISPN-6079: --------------------------------- Summary: Searching nodes by IP doesn't work Key: ISPN-6079 URL: https://issues.jboss.org/browse/ISPN-6079 Project: Infinispan Issue Type: Bug Components: Console Reporter: Roman Macor Searching nodes by IP address doesn't work. e.g. 127.0.0.1 Result: No nodes are matched. Note: searching by part of address - "127.0" works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5937) HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5937?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5937: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3928 > HotRod client ExpiryTest.testGlobalExpiryPutWithFlag random failures > -------------------------------------------------------------------- > > Key: ISPN-5937 > URL: https://issues.jboss.org/browse/ISPN-5937 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 8.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Martin Vrabel > Priority: Critical > Labels: testsuite_stability > Fix For: 8.2.0.Alpha1 > > Attachments: ExpiryTest.log.gz > > > The put operation succeeds, but the get immediately afterwards doesn't find the entry: > {noformat} > java.lang.AssertionError: expected:<v1> but was:<null> > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108) > at org.infinispan.client.hotrod.ExpiryTest.expectCachedThenExpired(ExpiryTest.java:103) > at org.infinispan.client.hotrod.ExpiryTest.expectExpiryAfterRequest(ExpiryTest.java:99) > at org.infinispan.client.hotrod.ExpiryTest.testGlobalExpiryPutWithFlag(ExpiryTest.java:46){noformat} > http://ci.infinispan.org/viewLog.html?buildId=31770&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016