July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-330) Pipeline Support For Productised Kiali

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-330?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-330: ------------------------------- Workflow: GIT Pull Request workflow (was: classic default workflow) Parent: SWSQE-331 Issue Type: Sub-task (was: QE Task) > Pipeline Support For Productised Kiali > -------------------------------------- > > Key: SWSQE-330 > URL: https://issues.jboss.org/browse/SWSQE-330 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-331) Support Produtized Builds

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-331: ---------------------------------- Summary: Support Produtized Builds Key: SWSQE-331 URL: https://issues.jboss.org/browse/SWSQE-331 Project: Kiali QE Issue Type: Story Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10686) Fixing DS statistics tests after JBJCA-1375

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-10686?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-15024 to WFLY-10686: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10686 (was: JBEAP-15024) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA Test Suite (was: JCA) (was: Test Suite) Fix Version/s: (was: 7.1.4.GA) > Fixing DS statistics tests after JBJCA-1375 > ------------------------------------------- > > Key: WFLY-10686 > URL: https://issues.jboss.org/browse/WFLY-10686 > Project: WildFly > Issue Type: Bug > Components: JCA, Test Suite > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > JBJCA-1375 is changing when JCA pool statistics are reset. Originally the stats were reset whenever {{setEnabled(boolean)}} was called, no matter the value. In the changed impl the reset only happens if the {{enabled}} value has changed. > Broken testsuite run: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=127885& -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-330) Pipeline Support For Productised Kiali

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-330: ---------------------------------- Summary: Pipeline Support For Productised Kiali Key: SWSQE-330 URL: https://issues.jboss.org/browse/SWSQE-330 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-288) Kiali - Istio Checker to 0.8.0

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-288?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-288. -------------------------------- Resolution: Done > Kiali - Istio Checker to 0.8.0 > ------------------------------ > > Key: SWSQE-288 > URL: https://issues.jboss.org/browse/SWSQE-288 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil kondkar > Priority: Minor > > We have a job http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Istio-Checker > which checks Istio installation on OC. It works with 0.7.1 Istio. > Main jenkins pipeline is switched to Istio 0.8.0 already. > TODO > Update this job and the script to support Istio 0.8.0 version pods which are: > grafana-cd99bf478-2k9zj 1/1 Running 0 19m > istio-citadel-ff5696f6f-6m8rv 1/1 Running 0 19m > istio-cleanup-old-ca-qmd7k 0/1 Completed 0 19m > istio-egressgateway-58d98d898c-4qhx9 0/1 CrashLoopBackOff 7 19m > istio-ingressgateway-6bc7c7c4bc-867sz 0/1 CrashLoopBackOff 7 19m > istio-mixer-post-install-kjhhk 0/1 Completed 0 19m > istio-pilot-6c5c6b586c-gq6gt 2/2 Running 0 19m > istio-policy-5c7fbb4b9f-j2jjd 2/2 Running 0 19m > istio-sidecar-injector-dbd67c88d-ffkgm 1/1 Running 0 19m > istio-statsd-prom-bridge-6dbb7dcc7f-fcl8f 1/1 Running 0 19m > istio-telemetry-54b5bf4847-5wq78 2/2 Running 0 19m > istio-tracing-67dbb5b89f-l52vk 1/1 Running 0 19m > prometheus-586d95b8d9-dw9xl 1/1 Running 0 19m > servicegraph-6d86dfc6cb-25qtp 1/1 Running 1 19m -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-279) Pipeline to Istio 0.8.0

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-279?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-279. -------------------------------- Resolution: Done > Pipeline to Istio 0.8.0 > ----------------------- > > Key: SWSQE-279 > URL: https://issues.jboss.org/browse/SWSQE-279 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2655: ---------------------------------------- [~jomarko] I've included a change to sort them alphabetically (seemed a good idea to me). [~tari_manga] IDK if there are runtime considerations however it seems a good default and Users can re-order columns if they like. > [DMN Designer]: Decision Table: Automatically create input columns for each InputData element > --------------------------------------------------------------------------------------------- > > Key: DROOLS-2655 > URL: https://issues.jboss.org/browse/DROOLS-2655 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created. > - For simple data types the input column names should correspond exactly to InputData elements. > - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ... > h3. PR Manual Acceptance Test > - Check Decision Table Decision node, with inputs (?) > - Check Decision Table Decision node, without inputs > - Check Non Decision Table Decision node, with inputs > - Check Non Decision Table Decision node, without inputs > - Check Decision Table BKM node, with inputs > - Check Decision Table BKM node, without inputs > - Check Non Decision Table BKM node, with inputs > - Check Non Decision Table BKM node, without inputs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10685) Fix org.jboss.metadata.merge package export by multiple jars

by Richard Opalka (JIRA)

Richard Opalka created WFLY-10685: ------------------------------------- Summary: Fix org.jboss.metadata.merge package export by multiple jars Key: WFLY-10685 URL: https://issues.jboss.org/browse/WFLY-10685 Project: WildFly Issue Type: Bug Components: EE Reporter: Richard Opalka Fix For: 14.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10640) driver-datasource-class-name and driver-xa-datasource-class-name need to be validated when updating

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-10640?page=com.atlassian.jira.plugin... ] Stefano Maestri commented on WFLY-10640: ---------------------------------------- [~gaol] I think it would be more correct validating implementation. Tests need fixes. > driver-datasource-class-name and driver-xa-datasource-class-name need to be validated when updating > --------------------------------------------------------------------------------------------------- > > Key: WFLY-10640 > URL: https://issues.jboss.org/browse/WFLY-10640 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Minor > > Download oracle jdbc driver at http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-311... > Install the driver as a module and add the JDBC driver: > {code:bash} > module add --name=com.oracle.jdbc --resources=/opt/Downloads/ojdbc8.jar --dependencies=[javax.api, javax.transaction.api] > /subsystem=datasources/jdbc-driver=oracle:add(driver-name=oracle, driver-module-name=com.oracle.jdbc, driver-datasource-class-name=oracle.jdbc.datasource.OracleDataSource, driver-xa-datasource-class-name=oracle.jdbc.xa.client.OracleXADataSource, driver-class-name=oracle.jdbc.OracleDriver) > {code} > It should fail because the configuraiton: > {code:java} > driver-datasource-class-name=oracle.jdbc.datasource.OracleDataSource > {code} > is wrong, +oracle.jdbc.datasource.OracleDataSource+ is an interface, not a concrete class. > It should be the same for the data-source creation when specifying the datasource-class. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6597) IJ020017: Invalid archive deploying activemq-rar

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-6597?page=com.atlassian.jira.plugin.... ] Stefano Maestri reassigned WFLY-6597: ------------------------------------- Assignee: Tomasz Adamski (was: Stefano Maestri) > IJ020017: Invalid archive deploying activemq-rar > ------------------------------------------------ > > Key: WFLY-6597 > URL: https://issues.jboss.org/browse/WFLY-6597 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Final > Environment: CentOS 6 > Oracle Java 1.8.0_92-b14 > Wildfly 10.0.0.Final > ActiveMQ RAR 5.13.3 > Reporter: Brett Delle Grazie > Assignee: Tomasz Adamski > > Deploying ActiveMQ RAR via 'deploy' command: > deploy /opt/activemq/activemq-rar-5.13.3.rar > Results in the following log entry: > 2016-05-09 08:07:20,788 WARN [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-1) IJ020017: Invalid archive: file:/tmp/wildfly/vfs/temp/temp3cb3b15524db2617/content-d69689ded82e9101/contents/ > repeated slightly later: > 2016-05-09 08:07:20,983 WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020017: Invalid archive: file:/tmp/wildfly/vfs/temp/temp3cb3b15524db2617/content-d69689ded82e9101/contents/ > However deployment is successful > Note that if a runtime-name is provided the RAR is *not* registered correctly. > See also previous issue raised WFLY-4431 (minimal info) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018