August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-906) Create auto-generated email with code coverage results

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-906?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-906: ------------------------------------- It was necessary to change System Admin e-mail address in jenkins config to Jenkins <jenkins2-kiali-qe(a)redhat.com>. It seems that mailing lists block other than '@redhat.com ' addresses. > Create auto-generated email with code coverage results > ------------------------------------------------------ > > Key: SWSQE-906 > URL: https://issues.jboss.org/browse/SWSQE-906 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: automation > > The email should report code coverage for dev tests, QE tests and trends. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4414?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reassigned DROOLS-4414: ---------------------------------------- Assignee: Gabriele Cardosi (was: Daniele Zonca) > Scenario Simulation model versions are incompatible > --------------------------------------------------- > > Key: DROOLS-4414 > URL: https://issues.jboss.org/browse/DROOLS-4414 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip > > > There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. > The incompatibility can be spotted for example: > - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 > - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 > - Try to open the *test-salary.scesim* file > - The error user will see is attached -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4414?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4414: -------------------------------- Description: There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. The incompatibility can be spotted for example: - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 - Try to open the *test-salary.scesim* file - The error user will see is attached was: There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. The incompatibility can be spotted for example: - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 - The error user will see is attached > Scenario Simulation model versions are incompatible > --------------------------------------------------- > > Key: DROOLS-4414 > URL: https://issues.jboss.org/browse/DROOLS-4414 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip > > > There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. > The incompatibility can be spotted for example: > - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 > - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 > - Try to open the *test-salary.scesim* file > - The error user will see is attached -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4414: ----------------------------------- Summary: Scenario Simulation model versions are incompatible Key: DROOLS-4414 URL: https://issues.jboss.org/browse/DROOLS-4414 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.25.0.Final Reporter: Jozef Marko Assignee: Daniele Zonca Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. The incompatibility can be spotted for example: - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 - The error user will see is attached -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4414) Scenario Simulation model versions are incompatible

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4414?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4414: -------------------------------- Tester: Jozef Marko > Scenario Simulation model versions are incompatible > --------------------------------------------------- > > Key: DROOLS-4414 > URL: https://issues.jboss.org/browse/DROOLS-4414 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-08-06 11-42-52.png, dmn-scenario-7.4.cr2.zip > > > There is an incompatibility between Scenario Simulation 1.5 and 1.6 versions. > The incompatibility can be spotted for example: > - Create project on the RHPAM product 7.4.0, there is Scenario Simulation model version 1.5 > - Import such project into business central 7.25.0-SNAPSHOT, There is Scenario Simulation model version 1.6 > - The error user will see is attached -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12351) Upgrade Weld to 3.1.2.Final

by Matěj Novotný (Jira)

[ https://issues.jboss.org/browse/WFLY-12351?page=com.atlassian.jira.plugin... ] Matěj Novotný updated WFLY-12351: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12473 > Upgrade Weld to 3.1.2.Final > --------------------------- > > Key: WFLY-12351 > URL: https://issues.jboss.org/browse/WFLY-12351 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld > Reporter: Matěj Novotný > Assignee: Matěj Novotný > Priority: Major > Fix For: 18.0.0.Beta1 > > > Upgrade Weld to 3.1.2.Final and Weld API to 3.1.SP1. > More details on updates are here - http://weld.cdi-spec.org/news/2019/08/06/weld-312Final/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12351) Upgrade Weld to 3.1.2.Final

by Matěj Novotný (Jira)

Matěj Novotný created WFLY-12351: ------------------------------------ Summary: Upgrade Weld to 3.1.2.Final Key: WFLY-12351 URL: https://issues.jboss.org/browse/WFLY-12351 Project: WildFly Issue Type: Component Upgrade Components: CDI / Weld Reporter: Matěj Novotný Assignee: Matěj Novotný Fix For: 18.0.0.Beta1 Upgrade Weld to 3.1.2.Final and Weld API to 3.1.SP1. More details on updates are here - http://weld.cdi-spec.org/news/2019/08/06/weld-312Final/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-918) Clean-environment jenkins job sometimes stuck on deleting istio-operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-918?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-918. ------------------------------------------- Resolution: Done > Clean-environment jenkins job sometimes stuck on deleting istio-operator > ------------------------------------------------------------------------ > > Key: SWSQE-918 > URL: https://issues.jboss.org/browse/SWSQE-918 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/clean-environment is sometimes stuck on: > + cat maistra/maistra-operator.yaml > + ISTIO_OPERATOR_HUB=quay.io/maistra > + ISTIO_OPERATOR_IMAGE=istio-operator-ubi8 > + ISTIO_OPERATOR_TAG=0.12 > + envsubst > + oc delete -n istio-operator --ignore-not-found=true -f - > customresourcedefinition.apiextensions.k8s.io "controlplanes.istio.openshift.com" deleted > customresourcedefinition.apiextensions.k8s.io "servicemeshcontrolplanes.maistra.io" deleted > customresourcedefinition.apiextensions.k8s.io "servicemeshmemberrolls.maistra.io" deleted > clusterrole.rbac.authorization.k8s.io "maistra-admin" deleted > clusterrolebinding.rbac.authorization.k8s.io "maistra-admin" deleted > clusterrole.rbac.authorization.k8s.io "istio-admin" deleted > clusterrolebinding.rbac.authorization.k8s.io "istio-admin" deleted > clusterrole.rbac.authorization.k8s.io "istio-operator" deleted > serviceaccount "istio-operator" deleted > clusterrolebinding.rbac.authorization.k8s.io "istio-operator-account-istio-operator-cluster-role-binding" deleted > validatingwebhookconfiguration.admissionregistration.k8s.io "istio-operator.servicemesh-resources.maistra.io" deleted > service "admission-controller" deleted > deployment.apps "istio-operator" deleted > Running against OCP 4.1 cluster -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-918) Clean-environment jenkins job sometimes stuck on deleting istio-operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-918?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-918: ----------------------------------------------- It is because of finalizers. Look for finalizers on smmr and smcp on both control planes (istio-system and istio-system2). You can do via {code:bash} oc edit smmr -n istio-system oc edit smcp -n istio-system oc edit smmr -n istio-system2 oc edit smcp -n istio-system2 {code} then you can edit the object by removing the finalizers. It is not supposed to happen anymore because I added a while to remove the control plane namespace only if you had removed the smmr and smcp entirely first. Let me know if anything of this happen again. > Clean-environment jenkins job sometimes stuck on deleting istio-operator > ------------------------------------------------------------------------ > > Key: SWSQE-918 > URL: https://issues.jboss.org/browse/SWSQE-918 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/clean-environment is sometimes stuck on: > + cat maistra/maistra-operator.yaml > + ISTIO_OPERATOR_HUB=quay.io/maistra > + ISTIO_OPERATOR_IMAGE=istio-operator-ubi8 > + ISTIO_OPERATOR_TAG=0.12 > + envsubst > + oc delete -n istio-operator --ignore-not-found=true -f - > customresourcedefinition.apiextensions.k8s.io "controlplanes.istio.openshift.com" deleted > customresourcedefinition.apiextensions.k8s.io "servicemeshcontrolplanes.maistra.io" deleted > customresourcedefinition.apiextensions.k8s.io "servicemeshmemberrolls.maistra.io" deleted > clusterrole.rbac.authorization.k8s.io "maistra-admin" deleted > clusterrolebinding.rbac.authorization.k8s.io "maistra-admin" deleted > clusterrole.rbac.authorization.k8s.io "istio-admin" deleted > clusterrolebinding.rbac.authorization.k8s.io "istio-admin" deleted > clusterrole.rbac.authorization.k8s.io "istio-operator" deleted > serviceaccount "istio-operator" deleted > clusterrolebinding.rbac.authorization.k8s.io "istio-operator-account-istio-operator-cluster-role-binding" deleted > validatingwebhookconfiguration.admissionregistration.k8s.io "istio-operator.servicemesh-resources.maistra.io" deleted > service "admission-controller" deleted > deployment.apps "istio-operator" deleted > Running against OCP 4.1 cluster -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-918) Clean-environment jenkins job sometimes stuck on deleting istio-operator

by Filip Brychta (Jira)

Filip Brychta created SWSQE-918: ----------------------------------- Summary: Clean-environment jenkins job sometimes stuck on deleting istio-operator Key: SWSQE-918 URL: https://issues.jboss.org/browse/SWSQE-918 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Guilherme Baufaker Rêgo https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/clean-environment is sometimes stuck on: + cat maistra/maistra-operator.yaml + ISTIO_OPERATOR_HUB=quay.io/maistra + ISTIO_OPERATOR_IMAGE=istio-operator-ubi8 + ISTIO_OPERATOR_TAG=0.12 + envsubst + oc delete -n istio-operator --ignore-not-found=true -f - customresourcedefinition.apiextensions.k8s.io "controlplanes.istio.openshift.com" deleted customresourcedefinition.apiextensions.k8s.io "servicemeshcontrolplanes.maistra.io" deleted customresourcedefinition.apiextensions.k8s.io "servicemeshmemberrolls.maistra.io" deleted clusterrole.rbac.authorization.k8s.io "maistra-admin" deleted clusterrolebinding.rbac.authorization.k8s.io "maistra-admin" deleted clusterrole.rbac.authorization.k8s.io "istio-admin" deleted clusterrolebinding.rbac.authorization.k8s.io "istio-admin" deleted clusterrole.rbac.authorization.k8s.io "istio-operator" deleted serviceaccount "istio-operator" deleted clusterrolebinding.rbac.authorization.k8s.io "istio-operator-account-istio-operator-cluster-role-binding" deleted validatingwebhookconfiguration.admissionregistration.k8s.io "istio-operator.servicemesh-resources.maistra.io" deleted service "admission-controller" deleted deployment.apps "istio-operator" deleted Running against OCP 4.1 cluster -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 August 2019