October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4583) Allow to declaratively configure a SessionPool in the kmodule.xml

by Mario Fusco (Jira)

Mario Fusco created DROOLS-4583: ----------------------------------- Summary: Allow to declaratively configure a SessionPool in the kmodule.xml Key: DROOLS-4583 URL: https://issues.jboss.org/browse/DROOLS-4583 Project: Drools Issue Type: Feature Request Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-207) UX: Force removal of Operator upon delete - do not hang due to finalizers

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-207?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-207. ------------------------------ Verified in brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-operator:jb-eap-7.3-operator-rhel8-containers-candidate-33923-20190926082049 > UX: Force removal of Operator upon delete - do not hang due to finalizers > ------------------------------------------------------------------------- > > Key: WFWIP-207 > URL: https://issues.jboss.org/browse/WFWIP-207 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Petr Kremensky > Assignee: Ondrej Chaloupka > Priority: Blocker > Labels: operator > > We run yet into another use case where finalizers prevent users from deleting the project - the delete operation hangs. > pods: > {noformat} > $ oc get all > NAME READY STATUS RESTARTS AGE > pod/simple-jaxrs-operator-0 0/1 ImagePullBackOff 0 9m11s > pod/simple-jaxrs-operator-1 0/1 ImagePullBackOff 0 9m11s > pod/wildfly-operator-686846d6fb-db9sj 1/1 Running > $ oc delete wildflyserver simple-jaxrs-operator > wildflyserver.wildfly.org "simple-jaxrs-operator" deleted > ... hangs forever > {noformat} > operator log: > {noformat} > {"level":"info","ts":1569308322.2926116,"logger":"controller_wildflyserver","msg":"Reconciling WildFlyServer","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator"} > {"level":"info","ts":1569308322.2927597,"logger":"controller_wildflyserver","msg":"WildflyServer is marked for deletion. Waiting for finalizers to clean the workspace","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator"} > {"level":"info","ts":1569308322.2929516,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator","Pod Name":"simple-jaxrs-operator-0","IP Address":"10.128.0.227","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Pending"} > {"level":"info","ts":1569308322.2931426,"logger":"controller_wildflyserver","msg":"Transaction recovery scaledown processing","Request.Namespace":"pkremens-namespace","Request.Name":"simple-jaxrs-operator","Pod Name":"simple-jaxrs-operator-1","IP Address":"10.128.0.226","Pod State":"SCALING_DOWN_RECOVERY_INVESTIGATION","Pod Phase":"Pending"} > {"level":"error","ts":1569308322.294659,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"wildflyserver-controller","request":"pkremens-namespace/simple-jaxrs-operator","error":"Finalizer processing: failed transaction recovery for WildflyServer pkremens-namespace:simple-jaxrs-operator name Error: Found 2 errors:\n [[Pod 'simple-jaxrs-operator-0' / 'simple-jaxrs-operator' is in pending phase Pending. It will be hopefully started in a while. Transaction recovery needs the pod being fully started to be capable to mark it as clean for the scale down.]], [[Pod 'simple-jaxrs-operator-1' / 'simple-jaxrs-operator' is in pending phase Pending. It will be hopefully started in a while. Transaction recovery needs the pod being fully started to be capable to mark it as clean for the scale down.]],","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-l..."} > {noformat} > This is a call between safety vs. usability, but we believe that these issues (hanging delete command due to EAP7-1192) could be a serious usability problem for users. > *actual* > * scale down can require manual user interaction forced by finalizers > * delete can hang, requiring manual user interaction (delete deployment object, remove finalizer from operator CR, run delete again) > *expected* > * scale down can require manual user interaction forced by finalizers > * delete should never hang, it should be treated like a pulling a plug (rm -rf), in case users needs to make s graceful shutdown, he make a proper scale down to 0 prior the project deletion - this should be properly documented -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4582) Cell selection doesn't span the entire cell if you Insert RightMost Column

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4582: ------------------------------------ Summary: Cell selection doesn't span the entire cell if you Insert RightMost Column Key: DROOLS-4582 URL: https://issues.jboss.org/browse/DROOLS-4582 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Anna Dupliak Assignee: Yeser Amer Attachments: image-2019-10-01-10-50-42-411.png !image-2019-10-01-10-50-42-411.png|thumbnail! Selection doesn't span entirely if you bind new column -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4689) Upgrade jboss-remoting to 5.0.16.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4689?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4689: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-remoting to 5.0.16.Final > -------------------------------------- > > Key: WFCORE-4689 > URL: https://issues.jboss.org/browse/WFCORE-4689 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade JBoss Remoting to 5.0.16.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4522) Add an "expression" property for every complex type in Scenario Testing

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4522: ---------------------------------- Fix Version/s: (was: 7.6.0.Final) > Add an "expression" property for every complex type in Scenario Testing > ----------------------------------------------------------------------- > > Key: DROOLS-4522 > URL: https://issues.jboss.org/browse/DROOLS-4522 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Attachments: can-be-suspended-expression.webm > > > Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12615) Upgrade jboss-ejb-client to 4.0.24.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12615?page=com.atlassian.jira.plugin... ] Ivo Studensky updated WFLY-12615: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-ejb-client to 4.0.24.Final > ---------------------------------------- > > Key: WFLY-12615 > URL: https://issues.jboss.org/browse/WFLY-12615 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12615) Upgrade jboss-ejb-client to 4.0.24.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12615?page=com.atlassian.jira.plugin... ] Ivo Studensky moved JBEAP-17677 to WFLY-12615: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12615 (was: JBEAP-17677) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.2.0.GA) Fix Version/s: (was: 7.2.5.GA) > Upgrade jboss-ejb-client to 4.0.24.Final > ---------------------------------------- > > Key: WFLY-12615 > URL: https://issues.jboss.org/browse/WFLY-12615 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4574: --------------------------------------- [~uxdlc] Yes you are right. What do you mean with "more explicit"? > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-216) Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-216?page=com.atlassian.jira.plugin.... ] Jean Francois Denise reassigned WFWIP-216: ------------------------------------------ Assignee: Jean Francois Denise (was: Brian Stansberry) > Providing own ./configuration/settings.xml to S2I build doesn't work with galleon image > --------------------------------------------------------------------------------------- > > Key: WFWIP-216 > URL: https://issues.jboss.org/browse/WFWIP-216 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > Attachments: sti-custom-settings-galleon-image.log, sti-custom-settings-standard-cd-image.log > > > According to https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_fo... the user is able to provide its own settings.xml located in <app_dir>/configuration/settings.xml - this settings file then should be used for mvn build. > This clearly conflicts with galleon settings.xml. However, this is broken backward compatibility and should be somehow addressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-217) Customizing settings.xml via ENV variables doesn't work on galleon image

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-217?page=com.atlassian.jira.plugin.... ] Jean Francois Denise reassigned WFWIP-217: ------------------------------------------ Assignee: Jean Francois Denise (was: Brian Stansberry) > Customizing settings.xml via ENV variables doesn't work on galleon image > ------------------------------------------------------------------------ > > Key: WFWIP-217 > URL: https://issues.jboss.org/browse/WFWIP-217 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > > With released images it is possible to configure settings.xml used for S2I build via ENV variables, eg: https://github.com/jboss-openshift/cct_module/blob/1ff1d96/jboss/containe... > If I understood correctly this was introduced/changed by CLOUD-2911. But with galleon hooked into S2I the settings.xml is replaced with the one needed for slim server so this mechanism no longer works. > This is a backward compatibility issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019