[JBoss JIRA] (WFLY-10365) Generate component-matrix as part of the build
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/WFLY-10365?page=com.atlassian.jira.plugin... ]
Michal Jurc commented on WFLY-10365:
------------------------------------
It would be sweet if the {{wildfly/boms}} project could consume the component matrix versions without any required interaction besides just declaring versions in WildFly Component Matrix and then building {{wildfly/boms}}. Currently, the sync is rather complicated and not at all intuitive to implement.
> Generate component-matrix as part of the build
> ----------------------------------------------
>
> Key: WFLY-10365
> URL: https://issues.jboss.org/browse/WFLY-10365
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: David Lloyd
> Assignee: Kabir Khan
> Fix For: 13.0.0.Beta1
>
>
> Revert the change described in WFLY-9911.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10337) AuthenticationPolicyContextTestCase doesn't work with -Dnode{0, 1} properties
by Daniel Čihák (JIRA)
[ https://issues.jboss.org/browse/WFLY-10337?page=com.atlassian.jira.plugin... ]
Daniel Čihák resolved WFLY-10337.
---------------------------------
Resolution: Done
> AuthenticationPolicyContextTestCase doesn't work with -Dnode{0,1} properties
> ----------------------------------------------------------------------------
>
> Key: WFLY-10337
> URL: https://issues.jboss.org/browse/WFLY-10337
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Daniel Čihák
>
> *reproduce*
> {noformat}
> wildfly/testsuite/integration/ws] $ mvn clean test -Dtest=AuthenticationPolicyContextTestCase -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2
> ...
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'http://localhost:8080/picketlink-sts-ws/EchoService?wsdl'.: java.net.ConnectException: Connection refused (Connection refused)
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2198)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422)
> at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:266)
> at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:165)
> at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:85)
> ... 146 more
> {noformat}
> WSDL url
> {noformat}URL wsdl = new URL("http://localhost:8080/picketlink-sts-ws/EchoService?wsdl");{noformat} shouldn't be hardcoded. Please use {{TestSuiteEnvironment}} to build it instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures against wildfly-dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10325:
---------------------------------------
Apparently, the WildFly Test Suite: Integration - Web module is configured to run against the servlet distribution of server
{code:title=wildfly/testsuite/integration/web/pom.xml}
<properties>
...
<jboss.dist>${jbossas.project.dir}/${wildfly.web.build.output.dir}</jboss.dist>
...
</properties>
{code}
Running the tests against the servlet distribution works fine:
{noformat}
wildfly/testsuite] $ mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../servlet-dist/target/wildfly-servlet-13.0.0.Alpha1-SNAPSHOT)
...
[WARNING] Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
{noformat}
works fine. But we still need to be able to run the tests against the wildfly-dist in order to be able to run the integration tests against the prod builds.
> Test Suite: Integration - Web failures against wildfly-dist
> -----------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests start to fail once I point the testsuite a distribution via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10325) Test Suite: Integration - Web failures against wildfly-dist
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10325?page=com.atlassian.jira.plugin... ]
Petr Kremensky updated WFLY-10325:
----------------------------------
Summary: Test Suite: Integration - Web failures against wildfly-dist (was: Test Suite: Integration - Web failures with -Djboss.dist)
> Test Suite: Integration - Web failures against wildfly-dist
> -----------------------------------------------------------
>
> Key: WFLY-10325
> URL: https://issues.jboss.org/browse/WFLY-10325
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Petr Kremensky
> Assignee: Jan Stourac
>
> Web integration tests start to fail once I point the testsuite a distribution via jboss.dist property (the property is used to run the tests against productized builds or patched EAP distributions).
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -DskipTests
> cd testsuite
> mvn test -B -pl integration/web/
> # Tests run: 112, Failures: 0, Errors: 0, Skipped: 3
> mvn test -B -pl integration/web/ -Djboss.dist=$(realpath ../dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT)
> # Tests run: 109, Failures: 4, Errors: 9, Skipped: 3
> {noformat}
> There seems to be an issue with *WebCERTTestsSetup*, as once I enable the logs ( -DtestLogToFile=false ), the following errors appear.
> {noformat}
> 10:57:09,622 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "ssl-cert-realm")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.ssl-cert-realm.key-manager" => "Failed to start service
> Caused by: java.lang.IllegalStateException: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYDM0086: The KeyStore can not be found at /home/hudson/hudson_workspace/wildfly/testsuite/integration/web/target/WebCERTTestsSetup/server.keystore"},
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ]
Kevin Earls commented on SWSQE-200:
-----------------------------------
As a further update I asked [~fbrychta] to restart b24, and now I cannot create my elasticsearch instance at all. I am still getting the " grpc: the connection is unavailable" error.
I will leave it in this state if you want to do some investigation.
> B12 OpenShift Cluster is flaky
> ------------------------------
>
> Key: SWSQE-200
> URL: https://issues.jboss.org/browse/SWSQE-200
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
>
> I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances:
> 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail.
> 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear.
> So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
by Michael Anstis (JIRA)
Michael Anstis created DROOLS-2549:
--------------------------------------
Summary: [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
Key: DROOLS-2549
URL: https://issues.jboss.org/browse/DROOLS-2549
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.7.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
{{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
Changes required for this JIRA (split into sub-tasks when work starts):-
* Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
* Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
* Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2549:
-----------------------------------
Tester: Jozef Marko
> [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase
> -------------------------------------------------------------------
>
> Key: DROOLS-2549
> URL: https://issues.jboss.org/browse/DROOLS-2549
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes.
> At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}).
> Changes required for this JIRA (split into sub-tasks when work starts):-
> * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller
> * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children
> * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3075) KeyStore password as default KeyManager password
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3075?page=com.atlassian.jira.plugi... ]
Martin Choma commented on WFCORE-3075:
--------------------------------------
On the other hand, by providing this feature, breaking the keystore is matter of breaking weaker protection of both [1]. So it is question if we should support this bad practice.
[1] E. Security Considerations http://wp.internetsociety.org/ndss/wp-content/uploads/sites/25/2018/02/nd...
> KeyStore password as default KeyManager password
> ------------------------------------------------
>
> Key: WFCORE-3075
> URL: https://issues.jboss.org/browse/WFCORE-3075
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Security
> Reporter: Jan Kalina
> Priority: Critical
> Labels: keymanager, keystore, trustmanager
>
> In Elytron, there is keystore password (key-store resource) and key password (key-managers resource) required.
> However in theory there could be cases, where no password can be intended
> - key-store resource for truststore purposes (reading truststore) (but in legacy is password required)
> - PKCS12 can be created without key password (but keystore password in legacy is required)
> - you can create JKS programatically without keystore password
> - *in legacy key password is optional (which mean keystore password is used)*
> From discussion: We can make the password optional on the KeyManager so if no password is specified on the KeyManager we assume it is the one from the KeyStore.
> Created analysis document for this: https://developer.jboss.org/wiki/AnalysisDesign-KeyStorePasswordAsDefault...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months