May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-200: ------------------------------------------ Priority: Minor (was: Blocker) > 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

1
0
0 / 0

[JBoss JIRA] (JGRP-2267) RELAY2: notification when node becomes site master or ceases to be site master

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2267?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2267. ---------------------------- Resolution: Done > RELAY2: notification when node becomes site master or ceases to be site master > ------------------------------------------------------------------------------ > > Key: JGRP-2267 > URL: https://issues.jboss.org/browse/JGRP-2267 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.12 > > > Add a method to RELAY2 to add/remove notification listeners that are notified when the member becomes (or ceases to be) site master. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2267) RELAY2: notification when node becomes site master or ceases to be site master

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2267?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2267: -------------------------------- Added {{RELAY2.setSiteMasterListener(Consumer<Boolean>> l)}}. The listener is called with arg=={{true}} when a member became site master and {{false}} after it ceased being site master. > RELAY2: notification when node becomes site master or ceases to be site master > ------------------------------------------------------------------------------ > > Key: JGRP-2267 > URL: https://issues.jboss.org/browse/JGRP-2267 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.12 > > > Add a method to RELAY2 to add/remove notification listeners that are notified when the member becomes (or ceases to be) site master. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2267) RELAY2: notification when node becomes site master or ceases to be site master

by Bela Ban (JIRA)

Bela Ban created JGRP-2267: ------------------------------ Summary: RELAY2: notification when node becomes site master or ceases to be site master Key: JGRP-2267 URL: https://issues.jboss.org/browse/JGRP-2267 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 4.0.12 Add a method to RELAY2 to add/remove notification listeners that are notified when the member becomes (or ceases to be) site master. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-10339: ------------------------------------ [~pferraro] thanks for looking at it. I agree that we can split the resources as they have quite different cap/reqs. Could I suggest that we keep the <broadcast|discovery>-group for the JGroups implementation (which is the default we use)? The socket-based version would be named socket-broadcast-group as you suggest. Note that this has an impact on the legacy messaging migration. if the socket version is used, the migrated add operation will have to use the new resource name at https://github.com/wildfly/wildfly/blob/f4b6b3afdea148862a28b34082c8dd215.... Please note that I am about to revert the management version bump of the messaging-activemq subsystem as there has been no management changes between WildFly 12 and 13. If you plan to do that *before* WildFly 13, please tell me so that I cancel the revert. thanks! > Broadcast/discovery-group resources have ambiguous requirement specs > -------------------------------------------------------------------- > > Key: WFLY-10339 > URL: https://issues.jboss.org/browse/WFLY-10339 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Jeff Mesnil > > Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. > I suggest splitting these resources into 2: > {code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code} > which requires clustering capabilities > and > {code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code} > which requires a socket-binding capability. > This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2441: ---------------------------------------- Added a porting of this test into kieserver integration test with http://github.com/kiegroup/droolsjbpm-integration/commit/985fbcb9a > DMN runtime not using the kiecontainer root classloader to load classes > ----------------------------------------------------------------------- > > Key: DROOLS-2441 > URL: https://issues.jboss.org/browse/DROOLS-2441 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Priority: Blocker > Fix For: 7.8.0.Final > > Attachments: Standard Deviation.dmn, StandardDeviation.java > > > The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > {code:title=FunctionDefNode.java} > // might need to explicitly use a classloader here > Class<?> clazz = Class.forName( clazzName ); > {code} > To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3786) ManagementAuthenticationUsersTestCase fails on latest JDKs

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3786?page=com.atlassian.jira.plugi... ] Petr Kremensky commented on WFCORE-3786: ---------------------------------------- I can confirm we see this too with jdk1.8.0_b17x. This also causes running the tests of {{WildFly Test Suite: Integration - Elytron}} to fail with: {noformat} [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.1.Final:execute-commands (default) on project wildfly-ts-integ-elytron: Failed to execute commands: See /home/pkremens/devel/wildfly/testsuite/integration/elytron/target/wildfly-plugin.log for full details of failure. [ERROR] Caused by: java.io.IOException: Invalid secret key format"}}, [ERROR] "rolled-back" => true, [ERROR] "response-headers" => {"process-state" => "reload-required"} [ERROR] } {noformat} {noformat} { "outcome" => "failed", "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store.cred-store-default" => "WFLYELY00004: Unable to start the service. Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store Caused by: java.io.IOException: Invalid secret key format"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {noformat} > ManagementAuthenticationUsersTestCase fails on latest JDKs > ---------------------------------------------------------- > > Key: WFCORE-3786 > URL: https://issues.jboss.org/browse/WFCORE-3786 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Fix For: 5.0.0.Beta2 > > > I downloaded both jdk1.8.0_b171 & jdk1.8.0_b172. > When running whole WFCORE test suite on them > I'm getting InvalidUserStore exception in > ManagementAuthenticationUsersTestCase -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1567) [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/ELY-1567?page=com.atlassian.jira.plugin.s... ] Rostislav Svoboda updated ELY-1567: ----------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron-tool/pull/144, https://github.com/wildfly-security/wildfly-elytron-tool/pull/145 (was: https://github.com/wildfly-security/wildfly-elytron-tool/pull/144) > [JDK9+] wildfly-elytron-tool jar doesn't not have Multi-Release entry in Manifest > --------------------------------------------------------------------------------- > > Key: ELY-1567 > URL: https://issues.jboss.org/browse/ELY-1567 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Critical > > Split of https://issues.jboss.org/browse/WFLY-10256 to component trackers > Artifact wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR as it has overlay directory but no Multi-Release entry in Manifest -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3839) Cannot read-identity of filesystem-realm if change level attribute later

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3839?page=com.atlassian.jira.plugi... ] Martin Choma commented on WFCORE-3839: -------------------------------------- Does this prevent changing attribute manually in standalone.xml? Do we have such creation only attributes in model now? > Cannot read-identity of filesystem-realm if change level attribute later > ------------------------------------------------------------------------ > > Key: WFCORE-3839 > URL: https://issues.jboss.org/browse/WFCORE-3839 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Darran Lofthouse > > Add filesystem-realm, add a identity, then change the levels to 3, the previously added identity cannot be recovered anymore. This is due to the directory structure previously created. Perhaps, the levels attribute should be set at creation time only ? > {code} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:add(path=file_realm) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:add-identity(identity=user1) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:read-identity(identity=user1) > { > "outcome" => "success", > "result" => { > "name" => "user1", > "attributes" => undefined > } > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:write-attribute(name=levels,value=3) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] reload > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=file_realm1:read-identity(identity=user1) > { > "outcome" => "failed", > "failure-description" => "WFLYELY01002: Identity with name [user1] not found.", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2274) "?" special variable support

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2274?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2274: --------------------------------------- PR with additional tests is here: https://github.com/kiegroup/drools/pull/1898 > "?" special variable support > ---------------------------- > > Key: DROOLS-2274 > URL: https://issues.jboss.org/browse/DROOLS-2274 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Fedor Gavrilov > Assignee: Edson Tirelli > Fix For: 7.8.0.Final > > Attachments: DMN12-71_proposal_v3.docx > > > DMN 1.2 includes the support for extended unary tests that are basically expression in decision table cells that include the special variable '?'. See attached proposal. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018