November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-210) Operator missing way to configure multiple containers inside pod

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-210?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-210. -------------------------------- Resolution: Done Now tracked as EAP7-1392 > Operator missing way to configure multiple containers inside pod > ---------------------------------------------------------------- > > Key: WFWIP-210 > URL: https://issues.jboss.org/browse/WFWIP-210 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > User scenario: As a user I am able to run multiple containers under pod > - init container pattern [1] > - side car container pattern [1] > Note, this is pattern which {{istio}} use. > [1] https://matthewpalmer.net/kubernetes-app-developer/articles/multi-contain... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-219) Operator is missing node/pod affinity setting

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-219?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-219. -------------------------------- Resolution: Done Now tracked as EAP7-1390 > Operator is missing node/pod affinity setting > --------------------------------------------- > > Key: WFWIP-219 > URL: https://issues.jboss.org/browse/WFWIP-219 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to configure pod/node affinity > {code:yaml} > affinity: > nodeAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAntiAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > nodeName: > nodeSelector: > schedulerName > tolerations" > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-197) Operator missing shared storage between containers or pods

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-197?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-197. -------------------------------- Resolution: Deferred Now tracked as EAP7-1393 > Operator missing shared storage between containers or pods > ---------------------------------------------------------- > > Key: WFWIP-197 > URL: https://issues.jboss.org/browse/WFWIP-197 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > Operator is missing way of configuring volumes such > - it can be shared between containers in one pod (emptyDir) > - it can be shared between pods (Persistent Volume Claim) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-195) Operator does not provide way to configure https

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-195?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-195. -------------------------------- Resolution: Deferred Now tracked as EAP7-1389 > Operator does not provide way to configure https > ------------------------------------------------ > > Key: WFWIP-195 > URL: https://issues.jboss.org/browse/WFWIP-195 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > Operator is missing way of configuring > - https port, e.g. 8443 > - termination policy (passthrough, edge, reencrypt) > - way to specify certificates -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-194) Operator does not provide way to expose arbitrary port

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-194?page=com.atlassian.jira.plugin.... ] Petr Kremensky closed WFWIP-194. -------------------------------- Resolution: Deferred Now tracked as EAP7-1395 > Operator does not provide way to expose arbitrary port > ------------------------------------------------------ > > Key: WFWIP-194 > URL: https://issues.jboss.org/browse/WFWIP-194 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Minor > Labels: operator > > Going through non-Operator approach scenarios we have identified Operator is missing this feature: way to expose arbitrary container port, e.g: > - https:8443 > - jolokia:8778 > - debugging:5000 > - dns-ping:8888 > - any app specific port > Could be partially workarounded by `oc port-forward` capability -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4763) Test Scenario: consider all columns even if an expression is available

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4763?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4763: ---------------------------------- Summary: Test Scenario: consider all columns even if an expression is available (was: Test Scenario: consider all the column even if an expression is available) > Test Scenario: consider all columns even if an expression is available > ---------------------------------------------------------------------- > > Key: DROOLS-4763 > URL: https://issues.jboss.org/browse/DROOLS-4763 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > - Create two GIVEN columns > - Map column1 to the whole object (expression) > - Map column2 to a field > - Write an expression in column1 and a value in column2 > - Run > The GIVEN object should be the composition of expression + value > For example: > - Expression: new Person("name", 10); > - Value (age): 15 > - Result: a Person instance with name "name" and age 15 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4763) Test Scenario: consider all columns of an instance even if an expression is available

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4763?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-4763: ---------------------------------- Summary: Test Scenario: consider all columns of an instance even if an expression is available (was: Test Scenario: consider all columns even if an expression is available) > Test Scenario: consider all columns of an instance even if an expression is available > ------------------------------------------------------------------------------------- > > Key: DROOLS-4763 > URL: https://issues.jboss.org/browse/DROOLS-4763 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > - Create two GIVEN columns > - Map column1 to the whole object (expression) > - Map column2 to a field > - Write an expression in column1 and a value in column2 > - Run > The GIVEN object should be the composition of expression + value > For example: > - Expression: new Person("name", 10); > - Value (age): 15 > - Result: a Person instance with name "name" and age 15 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4763) Test Scenario: consider all the column even if an expression is available

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4763: ------------------------------------- Summary: Test Scenario: consider all the column even if an expression is available Key: DROOLS-4763 URL: https://issues.jboss.org/browse/DROOLS-4763 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca - Create two GIVEN columns - Map column1 to the whole object (expression) - Map column2 to a field - Write an expression in column1 and a value in column2 - Run The GIVEN object should be the composition of expression + value For example: - Expression: new Person("name", 10); - Value (age): 15 - Result: a Person instance with name "name" and age 15 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12720) [18.0.1] Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12720?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12720: ------------------------------------ Fix Version/s: (was: 18.0.1.Final) > [18.0.1] Update BouncyCastle from 1.60 to 1.64 > ---------------------------------------------- > > Key: WFLY-12720 > URL: https://issues.jboss.org/browse/WFLY-12720 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Paul Ferraro edited comment on WFLY-12718 at 11/14/19 9:34 PM: --------------------------------------------------------------- [~tommaso-borgato] These last test runs seem to be using mod_jk, which we already established has problems with its configuration. Can you rerun commit 03ed572bd163648d77744ac5e0a034e360ce2691 with mod_cluster? was (Author: pferraro): [~tommaso-borgato] These last test runs seem to be using mod_jk, which we already established has problems with its configuration. Can you rerun with mod_cluster? > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2019