October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-478) Install Istioctl on the demand when is needed

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-478: --------------------------------------------- Summary: Install Istioctl on the demand when is needed Key: SWSQE-478 URL: https://issues.jboss.org/browse/SWSQE-478 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo When it is pre-installed instioctl, sometimes it may lead to a situation that istioctl uses a different version than istio files See SWSQE-475 for that situation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3216) Async dependencies resolution or add loading indicator during scesim creation

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3216: ------------------------------------- Summary: Async dependencies resolution or add loading indicator during scesim creation Key: DROOLS-3216 URL: https://issues.jboss.org/browse/DROOLS-3216 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca When user create the first scesim file in the project, the system creates the JUnit activator file and it adds the needed dependencies. After that the system takes several seconds (5-6) to retrieve all the dependencies. During this time the editor still blank without any indicator or information to the user about what is going on. This happens only for the first scesim creation in the project -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-477) REST Tests failed in Istio 1.0.3

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-477?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-477: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > REST Tests failed in Istio 1.0.3 > -------------------------------- > > Key: SWSQE-477 > URL: https://issues.jboss.org/browse/SWSQE-477 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > > Started happening after B12 installed with Istio 1.0.3. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-kiali-e2e-te... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-476) PRT Output Improve

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-476?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-476: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > PRT Output Improve > ------------------ > > Key: SWSQE-476 > URL: https://issues.jboss.org/browse/SWSQE-476 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Feedback from developers. > When PRT fails because of some internal reason, e.g. bookinfo install fails, devs are confused. Or if e2e tests fail for some other reason. > What we need to do, when PRT fails due to other reason that e2e tests broken by PR, then the bot should comment in PR that "PRT is broken, contact to QE". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-474) Update Upstream Pipeline to Support Istio 1.0.3

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-474?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-474: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > Update Upstream Pipeline to Support Istio 1.0.3 > ----------------------------------------------- > > Key: SWSQE-474 > URL: https://issues.jboss.org/browse/SWSQE-474 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Update Pipeline Jobs > - Istio Upstream > - Bookinfo > - Complex mesh -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-475) Bookinfo installation fails on B12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-475?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-475: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > Bookinfo installation fails on B12 > ---------------------------------- > > Key: SWSQE-475 > URL: https://issues.jboss.org/browse/SWSQE-475 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > Hi Guilherme, > Could you please take a look into this failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > Thanks, > Hayk -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11265) wildfly-feature-pack -- Dependency Error

by Dennis Gesker (Jira)

Dennis Gesker created WFLY-11265: ------------------------------------ Summary: wildfly-feature-pack -- Dependency Error Key: WFLY-11265 URL: https://issues.jboss.org/browse/WFLY-11265 Project: WildFly Issue Type: Bug Affects Versions: 14.0.0.Final Environment: Ubuntu 18.10 JDK 11 WildFly 14.0.1.Final Reporter: Dennis Gesker Assignee: Jason Greene Fix For: 14.0.0.Final In my gradle build I've added: * providedCompile "org.wildfly:wildfly-feature-pack:14.0.1.Final"* But, I'm getting: *> Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. Required by: project : > org.wildfly:wildfly-feature-pack:14.0.1.Final > org.glassfish.soteria:javax.security.enterprise:1.0* > Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. > Unable to load Maven meta-data from https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu.... > Could not get resource 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > Could not GET 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > extension (10) should not be presented in server_hello Presently I have the following repositories in my build: jcenter() mavenCentral() maven { name "Gradle Repository" url "https://plugins.gradle.org/m2/" } maven { name "JBoss Public Maven Repository Group" url "https://repository.jboss.org/nexus/content/groups/public-jboss/" } maven { name "JBoss Public Maven Repository Group" url "http://repository.jboss.org/nexus/content/groups/public/" } But, I suspect I am missing a repository specific to WildFly. Or, maybe there is a bad entry in the POM? Thanks, Dennis -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3214: ----------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type > - Function parameter is simple data type > - Multiple parameters -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin... ] Chao Wang reassigned WFLY-10654: -------------------------------- Assignee: (was: Chao Wang) > In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container. > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10654 > URL: https://issues.jboss.org/browse/WFLY-10654 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 13.0.0.Final > Reporter: Chao Wang > Priority: Major > > Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case . > From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below : > ~~~~ > 1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > 22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > ~~~~ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3106) Create a start.drools.org website

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3106?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3106: ------------------------------------- poker: 8 > Create a start.drools.org website > --------------------------------- > > Key: DROOLS-3106 > URL: https://issues.jboss.org/browse/DROOLS-3106 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Create a start website for Drools similar to what has been done for jBPM here: https://start.jbpm.org/ > Source code of jbpm web site are available here: https://start.jbpm.org/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018