March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-606) Move Complex Mesh to Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-606?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-606. ------------------------------------------- Resolution: Done > Move Complex Mesh to Kiali Test Mesh Operator > --------------------------------------------- > > Key: SWSQE-606 > URL: https://issues.jboss.org/browse/SWSQE-606 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Complex Mesh is an important mesh. It must be moved to KIali Test mesh operator because of the explanation on parent task. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-606) Move Complex Mesh to Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-606?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-606: ------------------------------------------ Git Pull Request: https://github.com/kiali/kiali-test-mesh/pull/41 > Move Complex Mesh to Kiali Test Mesh Operator > --------------------------------------------- > > Key: SWSQE-606 > URL: https://issues.jboss.org/browse/SWSQE-606 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Complex Mesh is an important mesh. It must be moved to KIali Test mesh operator because of the explanation on parent task. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-633) Separate the Resources on Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-633: --------------------------------------------- Summary: Separate the Resources on Kiali Test Mesh Operator Key: SWSQE-633 URL: https://issues.jboss.org/browse/SWSQE-633 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-534) Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-534: ------------------------------------------ Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #19 (was: Kiali Sprint #16, Kiali Sprint #17) > Kiali Test Mesh Operator > ------------------------ > > Key: SWSQE-534 > URL: https://issues.jboss.org/browse/SWSQE-534 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > Today, we do have some common situations concerning the meshes that we use to test istio and kiali > 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline > 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command. > 4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support > 3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific. > Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-582) Add REST Performance Test Cases in Polarion

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-582?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-582: ------------------------------------------ Sprint: Kiali Sprint #19 > Add REST Performance Test Cases in Polarion > ------------------------------------------- > > Key: SWSQE-582 > URL: https://issues.jboss.org/browse/SWSQE-582 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-632) Ansible Istio Upstream installer is not working because it is not installing the CRDs

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-632?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-632: ------------------------------------------ Sprint: Kiali Sprint #19 > Ansible Istio Upstream installer is not working because it is not installing the CRDs > ------------------------------------------------------------------------------------- > > Key: SWSQE-632 > URL: https://issues.jboss.org/browse/SWSQE-632 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Priority: Major > > Istio Upstream Installer does not contain the crd installation from Istio 1.1 > Upstream Issue: https://github.com/istio/istio/issues/12262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11812) Error trying to build the Quickstart README.html Files

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11812?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11812: --------------------------------------- Component/s: Quickstarts (was: Documentation) Assignee: Eduardo Martins > Error trying to build the Quickstart README.html Files > ------------------------------------------------------ > > Key: WFLY-11812 > URL: https://issues.jboss.org/browse/WFLY-11812 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Wolfgang Mayer > Assignee: Eduardo Martins > Priority: Minor > > When executing the command > > mvn clean generate-resources -Pdocs > > Quickstart: app-client - ear failes: > > INFO] Quickstart: messaging-clustering ................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 01:07 min > [INFO] Finished at: 2019-03-02T10:59:42+01:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project app-client-ear: Could not resolve dependencies for project org.wildfly.quickstarts:app-client-ear:ear:16.0.0.Final: The following artifacts could not be resolved: org.wildfly.quickstarts:app-client-client-simple:jar:16.0.0.Final, org.wildfly.quickstarts:app-client-ejb:jar:16.0.0.Final: Failure to find org.wildfly.quickstarts:app-client-client-simple:jar:16.0.0.Final in https://maven.repository.redhat.com/ga/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-enterprise-maven-repository has elapsed or updates are forced -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > mvn -v > Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) > Maven home: /apps/apache-maven-3.6.0 > Java version: 11.0.2, vendor: Oracle Corporation, runtime: /usr/java/jdk-11.0.2 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "4.12.14-lp150.12.48-default", arch: "amd64", family: "unix" > Either maven build or docs should be fixed. > Recommended workaround: "please use "mvn clean install -Pdocs". > (see also: https://developer.jboss.org/message/988269?et=watches.email.thread#988269) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-632) Ansible Istio Upstream installer is not working because it is not installing the CRDs

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-632: --------------------------------------------- Summary: Ansible Istio Upstream installer is not working because it is not installing the CRDs Key: SWSQE-632 URL: https://issues.jboss.org/browse/SWSQE-632 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Istio Upstream Installer does not contain the crd installation from Istio 1.1 Upstream Issue: https://github.com/istio/istio/issues/12262 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11817) CDI @Resource(lookup=...) processing does not start corresponding binding service

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11817?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-11817: -------------------------------- Description: If the corresponding binding service (the service responsible for creating the jndi binding) is not ACTIVE (e.g. clustering binding services are always PASSIVE) or, due to a race condition, has not yet started completely, a null value will be returned. The ee subsystem processes @Resource(lookup=...) correctly by establishing a dependency on the corresponding binder service. was: If the corresponding binding service (the service responsible for creating the jndi binding) is not ACTIVE (e.g. clustering binding services are always PASSIVE) or, due to a race condition, has not yet started completely, a null value will be returned. Compare this to the @Resource(lookup=...) processing in the ee subsystem, which correctly establishes a dependency on the corresponding binder service. > CDI @Resource(lookup=...) processing does not start corresponding binding service > --------------------------------------------------------------------------------- > > Key: WFLY-11817 > URL: https://issues.jboss.org/browse/WFLY-11817 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 16.0.0.Final > Reporter: Paul Ferraro > Assignee: Matej Novotny > Priority: Major > > If the corresponding binding service (the service responsible for creating the jndi binding) is not ACTIVE (e.g. clustering binding services are always PASSIVE) or, due to a race condition, has not yet started completely, a null value will be returned. > The ee subsystem processes @Resource(lookup=...) correctly by establishing a dependency on the corresponding binder service. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11817) CDI @Resource(lookup=...) processing does not start corresponding binding service

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11817?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-11817: -------------------------------- Workaround Description: Use a <resource-ref/> which references a <lookup-name/> via a <res-ref-name/> , and use @Resource(name = "...") instead. Workaround: Workaround Exists > CDI @Resource(lookup=...) processing does not start corresponding binding service > --------------------------------------------------------------------------------- > > Key: WFLY-11817 > URL: https://issues.jboss.org/browse/WFLY-11817 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 16.0.0.Final > Reporter: Paul Ferraro > Assignee: Matej Novotny > Priority: Major > > If the corresponding binding service (the service responsible for creating the jndi binding) is not ACTIVE (e.g. clustering binding services are always PASSIVE) or, due to a race condition, has not yet started completely, a null value will be returned. > Compare this to the @Resource(lookup=...) processing in the ee subsystem, which correctly establishes a dependency on the corresponding binder service. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

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 March 2019