[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]
Ok let me clarify better the flow:
# User creates a test scenario with also background data
# Run button is pressed (from the main tab)
# Execution fails because of error in background data (so pie chart red)
# *User realizes there are errors in background data <--- how does this work? Does user need to "find" the red indicator? *
# User switches to Background tab
# User fixes background data <--- red cells indicate error
This ticket is related to point 4, point 6 is already covered by red cells.
At the moment the only way to recognize that the errors are in Background (and then switch to that tab) is the small indicator you are proposing. Do we want to add anything more? A notification/a message/whatever?
> 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
> Attachments: background-error.png
>
>
> 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-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 edited comment on DROOLS-4625 at 10/16/19 4:51 AM:
-----------------------------------------------------------------
[~uxdlc]
Ok let me clarify better the flow:
# User creates a test scenario with also background data
# Run button is pressed (from the main tab)
# Execution fails because of error in background data (so pie chart red)
# *User realizes there are errors in background data <--- how does this work? Does user need to "find" the red indicator?*
# User switches to Background tab
# User fixes background data <--- red cells indicate error
This ticket is related to point 4, point 6 is already covered by red cells.
At the moment the only way to recognize that the errors are in Background (and then switch to that tab) is the small indicator you are proposing. Do we want to add anything more? A notification/a message/whatever?
was (Author: danielezonca):
[~uxdlc]
Ok let me clarify better the flow:
# User creates a test scenario with also background data
# Run button is pressed (from the main tab)
# Execution fails because of error in background data (so pie chart red)
# *User realizes there are errors in background data <--- how does this work? Does user need to "find" the red indicator? *
# User switches to Background tab
# User fixes background data <--- red cells indicate error
This ticket is related to point 4, point 6 is already covered by red cells.
At the moment the only way to recognize that the errors are in Background (and then switch to that tab) is the small indicator you are proposing. Do we want to add anything more? A notification/a message/whatever?
> 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
> Attachments: background-error.png
>
>
> 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] (WFWIP-251) Operator error logs on scale down
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-251?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil reassigned WFWIP-251:
---------------------------------
Assignee: Ondrej Chaloupka (was: Jeff Mesnil)
> Operator error logs on scale down
> ---------------------------------
>
> Key: WFWIP-251
> URL: https://issues.jboss.org/browse/WFWIP-251
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Ondrej Chaloupka
> Priority: Critical
> Labels: operator
> Attachments: operator-logs.txt
>
>
> Error messages can be found in operator logs after user performs a scale down task.
> *reproduce*
> * deploy operator {noformat}./build/run-openshift.sh{noformat}
> * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
> * wait for both replicas to be ready {noformat}oc get pods -w
> NAME READY STATUS RESTARTS AGE
> quickstart-0 1/1 Running 0 32s
> quickstart-1 1/1 Running 0 32s
> wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
> * scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
> * see the [^operator-logs.txt]
> *actual*
> Error messages in operator log
> {noformat}
> {"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {noformat}
> *expected*
> No error messages in operator log.
> Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFWIP-251) Operator error logs on scale down
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-251?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-251:
---------------------------------
Description:
Error messages can be found in operator logs after user performs a scale down task.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready {noformat}oc get pods -w
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 32s
quickstart-1 1/1 Running 0 32s
wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
* scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
* see the [^operator-logs.txt]
*actual*
Error messages in operator log
{noformat}
{"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{noformat}
*expected*
No error messages in operator log.
Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
was:
Error messages can be found in operator logs after user performs a scale down task.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready {noformat}oc get pods -w
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 32s
quickstart-1 1/1 Running 0 32s
wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
* scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
* see the operator logs [^operator-logs.txt]
*actual*
Error messages in operator log
{noformat}
{"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{noformat}
*expected*
No error messages in operator log.
Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
> Operator error logs on scale down
> ---------------------------------
>
> Key: WFWIP-251
> URL: https://issues.jboss.org/browse/WFWIP-251
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: operator
> Attachments: operator-logs.txt
>
>
> Error messages can be found in operator logs after user performs a scale down task.
> *reproduce*
> * deploy operator {noformat}./build/run-openshift.sh{noformat}
> * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
> * wait for both replicas to be ready {noformat}oc get pods -w
> NAME READY STATUS RESTARTS AGE
> quickstart-0 1/1 Running 0 32s
> quickstart-1 1/1 Running 0 32s
> wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
> * scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
> * see the [^operator-logs.txt]
> *actual*
> Error messages in operator log
> {noformat}
> {"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {noformat}
> *expected*
> No error messages in operator log.
> Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFWIP-251) Operator error logs on scale down
by Petr Kremensky (Jira)
Petr Kremensky created WFWIP-251:
------------------------------------
Summary: Operator error logs on scale down
Key: WFWIP-251
URL: https://issues.jboss.org/browse/WFWIP-251
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Petr Kremensky
Assignee: Jeff Mesnil
Attachments: operator-logs.txt
Error messages can be found in operator logs after user performs a scale down task.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready {noformat}oc get pods -w
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 32s
quickstart-1 1/1 Running 0 32s
wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
* scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
* see the operator logs
*actual*
Error messages in operator log
{noformat}
{"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{noformat}
*expected*
No error messages in operator log.
Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFWIP-251) Operator error logs on scale down
by Petr Kremensky (Jira)
[ https://issues.jboss.org/browse/WFWIP-251?page=com.atlassian.jira.plugin.... ]
Petr Kremensky updated WFWIP-251:
---------------------------------
Description:
Error messages can be found in operator logs after user performs a scale down task.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready {noformat}oc get pods -w
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 32s
quickstart-1 1/1 Running 0 32s
wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
* scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
* see the operator logs [^operator-logs.txt]
*actual*
Error messages in operator log
{noformat}
{"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{noformat}
*expected*
No error messages in operator log.
Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
was:
Error messages can be found in operator logs after user performs a scale down task.
*reproduce*
* deploy operator {noformat}./build/run-openshift.sh{noformat}
* deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
* wait for both replicas to be ready {noformat}oc get pods -w
NAME READY STATUS RESTARTS AGE
quickstart-0 1/1 Running 0 32s
quickstart-1 1/1 Running 0 32s
wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
* scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
* see the operator logs
*actual*
Error messages in operator log
{noformat}
{"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
{noformat}
*expected*
No error messages in operator log.
Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
> Operator error logs on scale down
> ---------------------------------
>
> Key: WFWIP-251
> URL: https://issues.jboss.org/browse/WFWIP-251
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Petr Kremensky
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: operator
> Attachments: operator-logs.txt
>
>
> Error messages can be found in operator logs after user performs a scale down task.
> *reproduce*
> * deploy operator {noformat}./build/run-openshift.sh{noformat}
> * deploy quickstart project from operator repository {noformat}oc apply -f deploy/crds/quickstart-cr.yaml{noformat}
> * wait for both replicas to be ready {noformat}oc get pods -w
> NAME READY STATUS RESTARTS AGE
> quickstart-0 1/1 Running 0 32s
> quickstart-1 1/1 Running 0 32s
> wildfly-operator-5bcb545b46-2bjs8 1/1 Running 0 102s{noformat}
> * scale down to 1 {noformat}oc patch wildflyserver quickstart -p '[{"op":"replace", "path":"/spec/replicas", "value":1}]' --type json{noformat}
> * see the operator logs [^operator-logs.txt]
> *actual*
> Error messages in operator log
> {noformat}
> {"level":"error","ts":1571213256.675551,"logger":"wildlfyserver_resources","msg":"Failed to update resource","WildFlyServer.Namespace":"wildfly-test","WildFlyServer.Name":"quickstart","Resource.Name":"quickstart","Resource.Type":"*v1.StatefulSet","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.6756332,"logger":"wildflyserver_controller","msg":"Failed to update StatefulSet.","StatefulSet.Namespace":"wildfly-test","StatefulSet.Name":"quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {"level":"error","ts":1571213256.675672,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"wildfly-test/quickstart","error":"Operation cannot be fulfilled on statefulsets.apps \"quickstart\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."}
> {noformat}
> *expected*
> No error messages in operator log.
> Operator image build from [0a221ea|https://github.com/wildfly/wildfly-operator/commit/0a221eac5eb462...]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (DROOLS-4650) GDST: Re-editing BRL columns causes NPE
by Toni Rikkola (Jira)
Toni Rikkola created DROOLS-4650:
------------------------------------
Summary: GDST: Re-editing BRL columns causes NPE
Key: DROOLS-4650
URL: https://issues.jboss.org/browse/DROOLS-4650
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor
Reporter: Toni Rikkola
Assignee: Toni Rikkola
The equals and hashcode implementations do not return equal results for BRL columns or equals expects the objects to be the same instance.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months
[JBoss JIRA] (WFWIP-250) How to install operator to watch list of namespaces?
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-250?page=com.atlassian.jira.plugin.... ]
Martin Choma updated WFWIP-250:
-------------------------------
Description:
We do not have eap operator on the stage OperatorHub WFWIP-232, so I could not try myself. But this questions arise.
{code:yaml|title=deploy/configmap-eap-operator.gen.yaml}
...
deployments:
- name: eap-operator
spec:
replicas: 1
selector:
matchLabels:
name: eap-operator
strategy: {}
template:
metadata:
labels:
name: eap-operator
spec:
containers:
- command:
- wildfly-operator
env:
- name: WATCH_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.annotations['olm.targetNamespaces']
...
{code}
{code:yaml|title=deploy/operator-group.yaml}
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: example
namespace: eap-operator
spec:
targetNamespaces:
- eap-operator
{code}
1. Does it mean operator by default watch only {{eap-operator}} namespace? Will that be parametrized in Web Console?
2. If user want to install operator to watch multiple/all namespaces how should he do? Will that be exposed in Web Console?
If I try to edit {{WATCH_NAMESPACE}} on eap-operator Deployment it is owerwriten back to
{code}
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: 'metadata.annotations[''olm.targetNamespaces'']'
{code}
was:
We do not have eap operator on the stage OperatorHub WFWIP-232, so I could not try myself. But this question has arise.
{code:yaml|title=deploy/configmap-eap-operator.gen.yaml}
...
deployments:
- name: eap-operator
spec:
replicas: 1
selector:
matchLabels:
name: eap-operator
strategy: {}
template:
metadata:
labels:
name: eap-operator
spec:
containers:
- command:
- wildfly-operator
env:
- name: WATCH_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.annotations['olm.targetNamespaces']...
{code}
{code:yaml|title=deploy/operator-group.yaml}
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: example
namespace: eap-operator
spec:
targetNamespaces:
- eap-operator
{code}
1. Does it mean operator by default watch only {{eap-operator}} namespace? Will that be parametrized in Web Console?
2. If user want to install operator to watch multiple/all namespaces how should he do? Will that be exposed in Web Console?
If I try to edit {{WATCH_NAMESPACE}} on eap-operator Deployment it is owerwriten back to
{code}
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: 'metadata.annotations[''olm.targetNamespaces'']'
{code}
> How to install operator to watch list of namespaces?
> ----------------------------------------------------
>
> Key: WFWIP-250
> URL: https://issues.jboss.org/browse/WFWIP-250
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> We do not have eap operator on the stage OperatorHub WFWIP-232, so I could not try myself. But this questions arise.
> {code:yaml|title=deploy/configmap-eap-operator.gen.yaml}
> ...
> deployments:
> - name: eap-operator
> spec:
> replicas: 1
> selector:
> matchLabels:
> name: eap-operator
> strategy: {}
> template:
> metadata:
> labels:
> name: eap-operator
> spec:
> containers:
> - command:
> - wildfly-operator
> env:
> - name: WATCH_NAMESPACE
> valueFrom:
> fieldRef:
> fieldPath: metadata.annotations['olm.targetNamespaces']
> ...
> {code}
> {code:yaml|title=deploy/operator-group.yaml}
> apiVersion: operators.coreos.com/v1
> kind: OperatorGroup
> metadata:
> name: example
> namespace: eap-operator
> spec:
> targetNamespaces:
> - eap-operator
> {code}
> 1. Does it mean operator by default watch only {{eap-operator}} namespace? Will that be parametrized in Web Console?
> 2. If user want to install operator to watch multiple/all namespaces how should he do? Will that be exposed in Web Console?
> If I try to edit {{WATCH_NAMESPACE}} on eap-operator Deployment it is owerwriten back to
> {code}
> valueFrom:
> fieldRef:
> apiVersion: v1
> fieldPath: 'metadata.annotations[''olm.targetNamespaces'']'
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 9 months