[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-167:
-----------------------------------
[~mchoma]yes, "standalone.xml via ConfigMap" must be flagged as unsupported for EAP CD / 7.3
> EAP Operator handling ConfigMap internally
> ------------------------------------------
>
> Key: WFWIP-167
> URL: https://issues.jboss.org/browse/WFWIP-167
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap.
> Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users.
> Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me.
> However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator.
> What do you think? Have you considered this approach?
> [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (SWSQE-945) Check OCP 4.2 installation in PSI
by Filip Brychta (Jira)
Filip Brychta created SWSQE-945:
-----------------------------------
Summary: Check OCP 4.2 installation in PSI
Key: SWSQE-945
URL: https://issues.jboss.org/browse/SWSQE-945
Project: Kiali QE
Issue Type: QE Task
Reporter: Filip Brychta
Assignee: Filip Brychta
OCP 4.2 should support installation on OpenStack out of the box. We need to check if it's possible in PSI
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-1771) Serialization is triggering rule multiple times
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-1771?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1771:
--------------------------------
Sprint: (was: 2019 Week 35-37)
> Serialization is triggering rule multiple times
> ------------------------------------------------
>
> Key: DROOLS-1771
> URL: https://issues.jboss.org/browse/DROOLS-1771
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.2.0.Final, 7.3.0.Final
> Reporter: Christopher Brecht
> Assignee: Mario Fusco
> Priority: Major
> Attachments: EventA.java, Person.java, Reproducer.java
>
>
> I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. You can see the output we expect without serialization.
> The EventA at 3:00:30 shouldn’t trigger the rule one at time 3:05:00. Using serialization, event/rule triggering seems to ignore the temporal order of timed events.
> +*WITH SERIALIZATION *+
> STATE OUT Fri Jan 01 03:03:00 CET 2010 com.reproducer.EventA@614aeccc[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
> STATE IN Fri Jan 01 03:05:00 CET 2010 com.reproducer.EventA@444548a0[value=0,timestamp=Fri Jan 01 03:00:30 CET 2010]
> STATE IN Fri Jan 01 03:05:00 CET 2010 com.reproducer.EventA@773c0293[value=0,timestamp=Fri Jan 01 03:04:00 CET 2010]
> STATE OUT Fri Jan 01 03:07:00 CET 2010 com.reproducer.EventA@319854f0[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
> STATE OUT Fri Jan 01 03:07:00 CET 2010 com.reproducer.EventA@415156bf[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]
> +*WITHOUT SERIALIZATION *+
> STATE OUT Fri Jan 01 03:03:00 CET 2010 com.reproducer.EventA@659925f4[value=1,timestamp=Fri Jan 01 03:02:00 CET 2010]
> STATE IN Fri Jan 01 03:05:00 CET 2010 com.reproducer.EventA@562c877a[value=0,timestamp=Fri Jan 01 03:04:00 CET 2010]
> STATE OUT Fri Jan 01 03:07:00 CET 2010 com.reproducer.EventA@3b569985[value=1,timestamp=Fri Jan 01 03:06:00 CET 2010]
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months