December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFCORE-5212) Remove Phase PARSE_EE_DEFAULT_BINDINGS_CONFIG

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5212?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5212: -------------------------------- Fix Version/s: 14.0.0.Beta4 (was: 14.0.0.Beta3) > Remove Phase PARSE_EE_DEFAULT_BINDINGS_CONFIG > --------------------------------------------- > > Key: WFCORE-5212 > URL: https://issues.redhat.com/browse/WFCORE-5212 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 14.0.0.Beta4 > > > This has been moved to STRUCTURE_EE_DEFAULT_BINDINGS_CONFIG -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2053) key-store-masked-password needs the elytron provider to be manually registered

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created ELY-2053: -------------------------------------------- Summary: key-store-masked-password needs the elytron provider to be manually registered Key: ELY-2053 URL: https://issues.redhat.com/browse/ELY-2053 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Affects Versions: 1.14.0.Final Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero When you use a {{wildfly-config.xml}} that uses the {{key-store-masked-password}} the wildfly provider needs to be manually registered. This [PasswordFactory.getInstance call|https://github.com/wildfly-security/wildfly-elytron/blob/1.14.0.Fina...] does not pass the providers as in the rest of the calls and tehrefore default providers in the JVM are used. The other problem is that the corresponding test [ElytronXmlParserTest|https://github.com/wildfly-security/wildfly-elytron/...] adds the provider so the error is hidden inside the tests. Just removing that line from the test you see the exception: {noformat} org.wildfly.client.config.ConfigXMLParseException: ELY01133: Failed to create credential at file:/home/rmartinc/wildfly-elytron/auth/client/target/test-classes/org/wildfly/security/auth/client/test-wildfly-config-v1_4.xml:38:245 at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreType$54(ElytronXmlParser.java:1977) at org.wildfly.security.auth.client.ElytronXmlParser$AbstractLoadingKeyStoreFactory.get(ElytronXmlParser.java:3640) at org.wildfly.security.auth.client.ElytronXmlParser$AbstractLoadingKeyStoreFactory.get(ElytronXmlParser.java:3624) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:385) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:261) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:225) at org.wildfly.security.auth.client.ElytronXmlParserTest.testKeyStoreClearPassword(ElytronXmlParserTest.java:117) Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "masked-HMAC-SHA1-AES-128" at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:122) at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:76) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreType$54(ElytronXmlParser.java:1973) ... 6 more {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5848) CallMethod with ActionFieldFunctions does not compile

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5848?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5848: -------------------------------- Description: [DROOLS-3893] [Guided Decision Table] Call method on is not generated - Red Hat Issue Tracker The DROOLS-3893 needs an additional fix for Call methods setups where the CallMethod uses ActionFieldFunctions. The problem appears when there is ActionCallMethod in a BRL before Set or Update column that is not BRL. The two columns use the same fact variable, so when searching by name the ActionCallMethod is found and we try to append the set/update to that. We should just ignore the call. was: [DROOLS-3893] [Guided Decision Table] Call method on is not generated - Red Hat Issue Tracker The DROOLS-3893 needs an additional fix for Call methods setups where the CallMethod uses ActionFieldFunctions. > CallMethod with ActionFieldFunctions does not compile > ------------------------------------------------------ > > Key: DROOLS-5848 > URL: https://issues.redhat.com/browse/DROOLS-5848 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > [DROOLS-3893] [Guided Decision Table] Call method on is not generated - Red Hat Issue Tracker > > The DROOLS-3893 needs an additional fix for Call methods setups where the CallMethod uses ActionFieldFunctions. > The problem appears when there is ActionCallMethod in a BRL before Set or Update column that is not BRL. The two columns use the same fact variable, so when searching by name the ActionCallMethod is found and we try to append the set/update to that. We should just ignore the call. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1255) UI Automations - Workload Pods from OC API

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1255?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1255: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/362 > UI Automations - Workload Pods from OC API > ------------------------------------------ > > Key: SWSQE-1255 > URL: https://issues.redhat.com/browse/SWSQE-1255 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5216: ---------------------------------------------- To reproduce the problem escape the env variables: oc set env dc/helloworld JBOSS_MODULEPATH=\${JBOSS_HOME}/modules:\${HOME} More generally, do we want to fix this problem? The use-case seems very un-common. [~jmesnil]? I we think that we need to fix this problem, then, I think that it should be solved at the CLOUD level, not at the wildfly-core level. One solution would be to patch the jboss-clis.sh script (we are already doing that in our images) to add the following line: JBOSS_MODULEPATH=$(eval "echo $JBOSS_MODULEPATH") To force evaluation of the env variable in the script. > EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set > ------------------------------------------------------------------------------------- > > Key: WFCORE-5216 > URL: https://issues.redhat.com/browse/WFCORE-5216 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages: > {noformat} > INFO Duration: 347 milliseconds > ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. > org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) > at org.jboss.modules.Main.main(Main.java:371) > {noformat} > This issue does not occur on JBoss EAP 7.2 container. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5216) EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5216?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5216: ---------------------------------------------- I tried to reproduce your problem. I observe that $JBOSS_HOME and $HOME are resolved in the local shell prior to be passed to Openshift. Could you call: oc set env dc/helloworld --list And report the value of JBOSS_MODULEPATH ? > EAP Pod fails to start when env JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} is set > ------------------------------------------------------------------------------------- > > Key: WFCORE-5216 > URL: https://issues.redhat.com/browse/WFCORE-5216 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > > Since JBoss EAP 7.3 for OpenShift, if environment variable JBOSS_MODULEPATH=${JBOSS_HOME}/modules:${HOME} which contains bash variable is set via DeploymentConfig, EAP Pod fails to start with the following messages: > {noformat} > INFO Duration: 347 milliseconds > ERROR Error applying /tmp/cli-configuration-script-1594252654.cli CLI script. > org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) > at org.jboss.modules.Main.main(Main.java:371) > {noformat} > This issue does not occur on JBoss EAP 7.2 container. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13932) Upgrade Bouncy Castle from 1.65 to 1.66

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13932?page=com.atlassian.jira.plugi... ] James Perkins closed WFLY-13932. -------------------------------- Resolution: Won't Do > Upgrade Bouncy Castle from 1.65 to 1.66 > --------------------------------------- > > Key: WFLY-13932 > URL: https://issues.redhat.com/browse/WFLY-13932 > Project: WildFly > Issue Type: Component Upgrade > Components: Security > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Release notes: https://www.bouncycastle.org/releasenotes.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1255) UI Automations - Workload Pods from OC API

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1255: ------------------------------------- Summary: UI Automations - Workload Pods from OC API Key: SWSQE-1255 URL: https://issues.redhat.com/browse/SWSQE-1255 Project: Kiali QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1255) UI Automations - Workload Pods from OC API

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1255?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1255: ---------------------------------- Sprint: Kiali Sprint #49 > UI Automations - Workload Pods from OC API > ------------------------------------------ > > Key: SWSQE-1255 > URL: https://issues.redhat.com/browse/SWSQE-1255 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14166) Upgrade WildFly Core to 14.0.0.Beta3

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-14166?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-14166: ------------------------------- Description: Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta3 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta2...14.0.0.Beta3 was: Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta2 Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta1...14.0.0.Beta2 > Upgrade WildFly Core to 14.0.0.Beta3 > ------------------------------------ > > Key: WFLY-14166 > URL: https://issues.redhat.com/browse/WFLY-14166 > Project: WildFly > Issue Type: Component Upgrade > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > Dev tag: https://github.com/wildfly/wildfly-core/releases/tag/14.0.0.Beta3 > Diff to previous integrated release: https://github.com/wildfly/wildfly-core/compare/14.0.0.Beta2...14.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020