April 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Vittorio Rigamonti (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Vittorio Rigamonti reopened ISPN-10113: --------------------------------------- This issue refers to the "config" field which should be under spec if we want to consider it part of the desired state of the object. > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10118: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/37 > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10118: ------------------------------------ Status: Open (was: New) > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Galder Zamarreño resolved ISPN-10113. ------------------------------------- Resolution: Duplicate Issue > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10113?page=com.atlassian.jira.plugin... ] Galder Zamarreño commented on ISPN-10113: ----------------------------------------- This is not completely. An operator is supposed to expose a status object, but that's independent of the `spec` field. This has already been caught by the operator scorecard, see ISPN-10118. > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.jboss.org/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Affects Versions: 0.2.1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10118) Add status field to Operator custom resource

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10118?page=com.atlassian.jira.plugin... ] Galder Zamarreño commented on ISPN-10118: ----------------------------------------- Status not shown: {code} $ kubectl get infinispan example-infinispan -n local-operators -o yaml apiVersion: infinispan.org/v1 config: {} kind: Infinispan metadata: ... spec: image: jboss/infinispan-server:latest size: 3 {code} After fix: {code} $ kubectl get infinispan example-infinispan -n local-operators -o yaml apiVersion: infinispan.org/v1 config: {} kind: Infinispan metadata: ... spec: image: jboss/infinispan-server:latest size: 3 status: nodes: - example-infinispan-0 - example-infinispan-1 - example-infinispan-2 {code} > Add status field to Operator custom resource > -------------------------------------------- > > Key: ISPN-10118 > URL: https://issues.jboss.org/browse/ISPN-10118 > Project: Infinispan > Issue Type: Enhancement > Components: Operator > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > > Operator scorecard warning > {code} > SUGGESTION: Add a 'status' field to your Custom Resource > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10121) Docs: Spring Boot Dependency

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10121?page=com.atlassian.jira.plugin... ] Donald Naro closed ISPN-10121. ------------------------------ Fix Version/s: (was: 9.4.13.Final) Resolution: Rejected > Docs: Spring Boot Dependency > ---------------------------- > > Key: ISPN-10121 > URL: https://issues.jboss.org/browse/ISPN-10121 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > > This issue affects the RHDG product docs even though the source is in the upstream repo. The downstream docs got out of sync with upstream. > :sb_starter: 1.0.5.Final-redhat-00001 > :sb2_starter: 2.1.3.Final-redhat-00001 > should be: > :sb_starter: 1.0.5.Final-redhat-00002 > :sb2_starter: 2.1.3.Final-redhat-00002 > https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10122) Unable to start application using Infinispan on Client/Server mode with JMX enabled

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10122?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10122: -------------------------------- Status: Open (was: New) > Unable to start application using Infinispan on Client/Server mode with JMX enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-10122 > URL: https://issues.jboss.org/browse/ISPN-10122 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 2.1.4.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > A Spring-Boot application using Infinispan Client/Server with JMX enabled for the Infinispan Client won't start, unless you disable jmx spring.jmx.enabled=false. > Infinispan already registers a bean that is registered by Spring, so we get the following exception on start: > {code} > org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [org.infinispan.client.hotrod.RemoteCacheManager@1d67f4e9] with key 'remoteCacheManager'; nested exception is javax.management.InstanceAlreadyExistsException: MXBean already registered with name org.infinispan:type=HotRodClient,name=Default > at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at java.base/java.util.HashMap.forEach(HashMap.java:1336) ~[na:na] > at org. > {code} > https://github.com/spring-projects/spring-boot/issues/16482 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10122) Unable to start application using Infinispan on Client/Server mode with JMX enabled

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10122?page=com.atlassian.jira.plugin... ] Katia Aresti reassigned ISPN-10122: ----------------------------------- Assignee: Katia Aresti > Unable to start application using Infinispan on Client/Server mode with JMX enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-10122 > URL: https://issues.jboss.org/browse/ISPN-10122 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 2.1.4.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > A Spring-Boot application using Infinispan Client/Server with JMX enabled for the Infinispan Client won't start, unless you disable jmx spring.jmx.enabled=false. > Infinispan already registers a bean that is registered by Spring, so we get the following exception on start: > {code} > org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [org.infinispan.client.hotrod.RemoteCacheManager@1d67f4e9] with key 'remoteCacheManager'; nested exception is javax.management.InstanceAlreadyExistsException: MXBean already registered with name org.infinispan:type=HotRodClient,name=Default > at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] > at java.base/java.util.HashMap.forEach(HashMap.java:1336) ~[na:na] > at org. > {code} > https://github.com/spring-projects/spring-boot/issues/16482 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10122) Unable to start application using Infinispan on Client/Server mode with JMX enabled

by Katia Aresti (Jira)

Katia Aresti created ISPN-10122: ----------------------------------- Summary: Unable to start application using Infinispan on Client/Server mode with JMX enabled Key: ISPN-10122 URL: https://issues.jboss.org/browse/ISPN-10122 Project: Infinispan Issue Type: Bug Components: Spring Integration Affects Versions: 2.1.4.Final Reporter: Katia Aresti A Spring-Boot application using Infinispan Client/Server with JMX enabled for the Infinispan Client won't start, unless you disable jmx spring.jmx.enabled=false. Infinispan already registers a bean that is registered by Spring, so we get the following exception on start: {code} org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [org.infinispan.client.hotrod.RemoteCacheManager@1d67f4e9] with key 'remoteCacheManager'; nested exception is javax.management.InstanceAlreadyExistsException: MXBean already registered with name org.infinispan:type=HotRodClient,name=Default at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) ~[spring-context-5.1.6.RELEASE.jar:5.1.6.RELEASE] at java.base/java.util.HashMap.forEach(HashMap.java:1336) ~[na:na] at org. {code} https://github.com/spring-projects/spring-boot/issues/16482 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2019