[JBoss JIRA] (DROOLS-4625) Scenario Test: UX for background data error reporting
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4625?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-4625:
---------------------------------------
[~uxdlc]
Yes this should be done during this sprint.
Btw this ticket is more like a question to answer rather then a design to produce.
We are implementing Background section based on this proposal https://issues.jboss.org/browse/DROOLS-4162 but it doesn't cover how to inform users of errors in background data.
As usual we validate data only when user runs the scenario but what if there is an error in background data?
We already know how to show a wrong value (red background in the cell) but it will be in another tab so I guess we should warn the user of that otherwise he will see you scenario failures but no red cells.
We can create a popup with a message like "There are errors in Background data. Do you want to open background tab? Yes/No" or maybe open background tab directly or maybe other?
> Scenario Test: UX for background data error reporting
> -----------------------------------------------------
>
> Key: DROOLS-4625
> URL: https://issues.jboss.org/browse/DROOLS-4625
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As a user I want to be informed about errors that occurred in the data I provided in the new *Background* tab. For more details about the *Backround* tab please see DROOLS-4162 and BAPL-1401.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Anna Dupliak (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Anna Dupliak updated DROOLS-4636:
---------------------------------
Description:
Update Scenario Cheatsheet for MVEL expression usage.
h3. Here are some topics that could be mentioned:
Expressions for Rule based scenarios for simple types
* Starts from "*#*"
* Runs for +properties+
* Runs for +duplicated+ properties
* Returns the +same+ type as property type in *GIVEN*
* Returns boolean in *EXPECTED*
* Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
* Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
* Could run any of java function for the project
* Exports and imports as any other value
Limitation for GIVEN
1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
Use case:
User inputs 1/2 to Integer property
2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
Use case:
User inputs inexistent MVEL function in one of the properties
3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
Use case:
User got one of the GIVEN fact expression excepted
4.Mvel +cannot be mixed+ with simple expressions in one cell
Use case:
For cell inputs :
{code:java}
[#4+4,68]
#actualvalue>1
{code}
was:
Update Scenario Cheatsheet for MVEL expression usage.
Here are some topics that could be mentioned:
Expressions for Rule based scenarios for simple types
Starts from "#"
Runs for properties
Runs for duplicated properties
Returns the same type as property type in GIVEN
Returns boolean in EXPECTED
Receives rule processed value as a parameter in EXPECTED via keyword "actualValue"
Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the EXPECTED value not a boolean
Could run any of java function for the project
Exports and imports as any other value
Limitation for GIVEN
1. Mvel expression results not property same type - drives scenario failure, error reason and highlighted
Use case:
User inputs 1/2 to Integer property
2.Mvel execution throws exception - drives scenario execution stopping, failure, error alert
Use case:
User inputs inexistent MVEL function in one of the properties
3.Mvel expression exception stops expression execution for all EXPECT colons
Use case:
User got one of the GIVEN fact expression excepted
4.It cannot be mixed with simple expressions in one cell
Use case:
For cell inputs :
[#4+4,68]
#actualvalue>1
Git Pull Request: https://github.com/kiegroup/drools/pull/2563#
> Update Scenario Cheatsheet to mention MVEL
> ------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitation for GIVEN
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Anna Dupliak (Jira)
[ https://issues.jboss.org/browse/DROOLS-4636?page=com.atlassian.jira.plugi... ]
Anna Dupliak updated DROOLS-4636:
---------------------------------
Description:
Update Scenario Cheatsheet for MVEL expression usage.
h3. Here are some topics that could be mentioned:
Expressions for Rule based scenarios for simple types
* Starts from "*#*"
* Runs for +properties+
* Runs for +duplicated+ properties
* Returns the +same+ type as property type in *GIVEN*
* Returns boolean in *EXPECTED*
* Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
* Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
* Could run any of java function for the project
* Exports and imports as any other value
Limitations
1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
Use case:
User inputs 1/2 to Integer property
2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
Use case:
User inputs inexistent MVEL function in one of the properties
3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
Use case:
User got one of the GIVEN fact expression excepted
4.Mvel +cannot be mixed+ with simple expressions in one cell
Use case:
For cell inputs :
{code:java}
[#4+4,68]
#actualvalue>1
{code}
was:
Update Scenario Cheatsheet for MVEL expression usage.
h3. Here are some topics that could be mentioned:
Expressions for Rule based scenarios for simple types
* Starts from "*#*"
* Runs for +properties+
* Runs for +duplicated+ properties
* Returns the +same+ type as property type in *GIVEN*
* Returns boolean in *EXPECTED*
* Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
* Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
* Could run any of java function for the project
* Exports and imports as any other value
Limitation for GIVEN
1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
Use case:
User inputs 1/2 to Integer property
2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
Use case:
User inputs inexistent MVEL function in one of the properties
3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
Use case:
User got one of the GIVEN fact expression excepted
4.Mvel +cannot be mixed+ with simple expressions in one cell
Use case:
For cell inputs :
{code:java}
[#4+4,68]
#actualvalue>1
{code}
> Update Scenario Cheatsheet to mention MVEL
> ------------------------------------------
>
> Key: DROOLS-4636
> URL: https://issues.jboss.org/browse/DROOLS-4636
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Affects Versions: 7.27.0.Final
> Reporter: Anna Dupliak
> Assignee: Daniele Zonca
> Priority: Minor
> Labels: CustomerFocus
>
> Update Scenario Cheatsheet for MVEL expression usage.
> h3. Here are some topics that could be mentioned:
> Expressions for Rule based scenarios for simple types
> * Starts from "*#*"
> * Runs for +properties+
> * Runs for +duplicated+ properties
> * Returns the +same+ type as property type in *GIVEN*
> * Returns boolean in *EXPECTED*
> * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*"
> * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean*
> * Could run any of java function for the project
> * Exports and imports as any other value
> Limitations
> 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+
> Use case:
> User inputs 1/2 to Integer property
> 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+
> Use case:
> User inputs inexistent MVEL function in one of the properties
> 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons
> Use case:
> User got one of the GIVEN fact expression excepted
> 4.Mvel +cannot be mixed+ with simple expressions in one cell
> Use case:
> For cell inputs :
> {code:java}
> [#4+4,68]
> #actualvalue>1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-4636:
------------------------------------
Summary: Update Scenario Cheatsheet to mention MVEL
Key: DROOLS-4636
URL: https://issues.jboss.org/browse/DROOLS-4636
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Affects Versions: 7.27.0.Final
Reporter: Anna Dupliak
Assignee: Daniele Zonca
Update Scenario Cheatsheet for MVEL expression usage.
Here are some topics that could be mentioned:
Expressions for Rule based scenarios for simple types
Starts from "#"
Runs for properties
Runs for duplicated properties
Returns the same type as property type in GIVEN
Returns boolean in EXPECTED
Receives rule processed value as a parameter in EXPECTED via keyword "actualValue"
Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the EXPECTED value not a boolean
Could run any of java function for the project
Exports and imports as any other value
Limitation for GIVEN
1. Mvel expression results not property same type - drives scenario failure, error reason and highlighted
Use case:
User inputs 1/2 to Integer property
2.Mvel execution throws exception - drives scenario execution stopping, failure, error alert
Use case:
User inputs inexistent MVEL function in one of the properties
3.Mvel expression exception stops expression execution for all EXPECT colons
Use case:
User got one of the GIVEN fact expression excepted
4.It cannot be mixed with simple expressions in one cell
Use case:
For cell inputs :
[#4+4,68]
#actualvalue>1
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12657) KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
by Martin Simka (Jira)
Martin Simka created WFLY-12657:
-----------------------------------
Summary: KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
Key: WFLY-12657
URL: https://issues.jboss.org/browse/WFLY-12657
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Martin Simka
Assignee: Radoslav Husar
In my test application on openshift KUBE_PING logs warning every 20-30s .
{noformat}
13:27:05,340 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12657) KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFLY-12657?page=com.atlassian.jira.plugin... ]
Martin Simka updated WFLY-12657:
--------------------------------
Forum Reference: https://developer.jboss.org/thread/280665
> KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12657
> URL: https://issues.jboss.org/browse/WFLY-12657
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.0.Final
> Reporter: Martin Simka
> Assignee: Radoslav Husar
> Priority: Major
>
> In my test application on openshift KUBE_PING logs warning every 20-30s .
> {noformat}
> 13:27:05,340 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12658) KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
by Martin Simka (Jira)
Martin Simka created WFLY-12658:
-----------------------------------
Summary: KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
Key: WFLY-12658
URL: https://issues.jboss.org/browse/WFLY-12658
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Martin Simka
Assignee: Radoslav Husar
In my test application on openshift KUBE_PING logs warning every 20-30s .
{noformat}
13:27:05,340 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFLY-12601) Eliminate StabilityMonitor usages in clustering subsystem
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-12601?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-12601:
-------------------------------------
[~ropalka] I've reworked runtime metrics/operations to use your suggested approach. Can you have a second look?
> Eliminate StabilityMonitor usages in clustering subsystem
> ---------------------------------------------------------
>
> Key: WFLY-12601
> URL: https://issues.jboss.org/browse/WFLY-12601
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Richard Opalka
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 19.0.0.Beta1
>
> Attachments: ServiceSupplier.png
>
>
> Clustering needs to eliminate usages of StabilityMonitor because SM is not reliable.
> It is possible that SM will prematurely inform about achieved stability even if it is not true.
> The reason is SM is not propagated up the dependencies chain and thus it may report
> about achieved stability even in case dependencies chain didn't finish its processing yet
> and 'real' stability wasn't achieved yet.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months