October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-977) Update PSI docs with additional resources

by Filip Brychta (Jira)

Filip Brychta created SWSQE-977: ----------------------------------- Summary: Update PSI docs with additional resources Key: SWSQE-977 URL: https://issues.jboss.org/browse/SWSQE-977 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4609) remove save method from editors that depend on upload widget

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4609?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-4609: -------------------------------------- These of course need to be double checked, but here you are: https://github.com/kiegroup/kie-wb-common/blob/6f3019ff62c3d52fd1ad161b9c... https://github.com/kiegroup/drools-wb/blob/cc0af48bf4a133bc592305fc1a4003... https://github.com/kiegroup/drools-wb/blob/08b3b308a82c6a7fefa7114dceedba... > remove save method from editors that depend on upload widget > ------------------------------------------------------------ > > Key: DROOLS-4609 > URL: https://issues.jboss.org/browse/DROOLS-4609 > Project: Drools > Issue Type: Task > Components: XLS Decision Table Editor, XLS Score Card Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > > The save method is never used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Yeray Borges commented on WFWIP-229: ------------------------------------ [~mjurc] We have created the required changes to allow the uses of the non-deprecated version of ASYM_ENCRYPT JGroups protocol. For ASYM_ENCRYPT now we have two possibilities in CD18: 1) Configure org.jgroups.protocols.ASYM_ENCRYPT (*deprecated version*): {noformat} docker run -it --rm --label working --network host \ -e CLI_DEBUG=true \ -e JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT \ -e JGROUPS_CLUSTER_PASSWORD=P@assw0rd \ jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:18.0 {noformat} If this configuration is used, in CD18 now we issue a WARN message: {{"WARN Detected missing JGroups encryption configuration for ASYM_ENCRYPT, the communication within the cluster will be encrypted using a deprecated version of ASYM_ENCRYPT protocol. You need to set all of these variables to configure ASYM_ENCRYPT using the Elytron keysore: JGROUPS_ENCRYPT_SECRET, JGROUPS_ENCRYPT_NAME, JGROUPS_ENCRYPT_PASSWORD, JGROUPS_ENCRYPT_KEYSTORE."}} In CD17 there is no alternative configuration; only the deprecated version of ASYM_ENCRYPT is available on the configuration. We considerate it as a bug fixed here. 2) ASYM_ENCRYPT (*non-deprecated version*). Only available in CD18. It uses Keystore configured in Elytron: {noformat} docker run -it --rm --label working --network host \ -e CLI_DEBUG=true \ -e JGROUPS_ENCRYPT_PROTOCOL="ASYM_ENCRYPT" \ -e JGROUPS_ENCRYPT_SECRET="encrypt_secret" \ -e JGROUPS_ENCRYPT_NAME="encrypt_name" \ -e JGROUPS_ENCRYPT_PASSWORD="encrypt_password" \ -e JGROUPS_ENCRYPT_KEYSTORE="encrypt_keystore" \ -e JGROUPS_CLUSTER_PASSWORD="cluster_password" \ jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:18.0 {noformat} Currently, if we use the same configuration in CD17, the following WARN is issued: {{WARN The specified JGroups configuration properties (JGROUPS_ENCRYPT_SECRET, JGROUPS_ENCRYPT_NAME, JGROUPS_ENCRYPT_PASSWORD, JGROUPS_ENCRYPT_KEYSTORE_DIR JGROUPS_ENCRYPT_KEYSTORE) will be ignored when using JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT. Only JGROUPS_CLUSTER_PASSWORD is used.}} That means the ignored variables used in CD17 are now used to configure the Elytron Keystore for the ASYM_ENCRYPT protocol in CD18, allowing us the configuration of the non-deprecated version of ASYM_ENCRYPT. In CD18, SYM_ENCRYPT and ASYM_ENCRYPT are now configured the same way to generate a non-deprecated versions. This possibility was not available before. > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > {code} > OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true > {code} > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Critical > > Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title=Example JGroups ASYM_ENCRYPT configuration} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-247) Rename s2i FP producer

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-247?page=com.atlassian.jira.plugin.... ] Jean Francois Denise updated WFWIP-247: --------------------------------------- Summary: Rename s2i FP producer (was: Rename producer s2i FP producer) > Rename s2i FP producer > ---------------------- > > Key: WFWIP-247 > URL: https://issues.jboss.org/browse/WFWIP-247 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > In order to help future migration from EAP CD to EAP, the galleon FP location should be: eap-s2i@maven(org.jboss.universe:s2i-universe) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12664) Upgrade jgroups-kubernetes to 1.0.13.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12664: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.13.Final Key: WFLY-12664 URL: https://issues.jboss.org/browse/WFLY-12664 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 19.0.0.Beta1 Solves: * KUBE_PING warning with StatefulSet * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update * Initial discovery ends up in singleton partitions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12663) Upgrade jgroups-kubernetes to 1.0.13.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12663?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12663: ---------------------------------- Fix Version/s: 19.0.0.Beta1 > Upgrade jgroups-kubernetes to 1.0.13.Final > ------------------------------------------ > > Key: WFLY-12663 > URL: https://issues.jboss.org/browse/WFLY-12663 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 19.0.0.Beta1 > > > Solves: > * KUBE_PING warning with StatefulSet > * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > * Initial discovery ends up in singleton partitions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[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 Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12657?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12657: ---------------------------------- Fix Version/s: 19.0.0.Beta1 > 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 > Fix For: 19.0.0.Beta1 > > > 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

1
0
0 / 0

[JBoss JIRA] (WFWIP-247) Rename producer s2i FP producer

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-247: ------------------------------------------ Summary: Rename producer s2i FP producer Key: WFWIP-247 URL: https://issues.jboss.org/browse/WFWIP-247 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Jean Francois Denise Assignee: Jean Francois Denise In order to help future migration from EAP CD to EAP, the galleon FP location should be: eap-s2i@maven(org.jboss.universe:s2i-universe) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Yeray Borges updated WFWIP-229: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-cekit-modules/pull/120, https://github.com/wildfly/temp-eap-modules/pull/66 > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > {code} > OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true > {code} > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Critical > > Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title=Example JGroups ASYM_ENCRYPT configuration} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-713) There is too many jenkins slaves

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-713?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-713: ------------------------------------- Previous parameters were not causing it. It seems it's related to slow b22 api when the slave is started but stays offline for a long time and meanwhile another one is started. > There is too many jenkins slaves > -------------------------------- > > Key: SWSQE-713 > URL: https://issues.jboss.org/browse/SWSQE-713 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > There are multiple jenkins slaves started for one jenkins job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019