June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-296) Kiali-on-Openshift Failing

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-296?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-296. ---------------------------------- Resolution: Done > Kiali-on-Openshift Failing > -------------------------- > > Key: SWSQE-296 > URL: https://issues.jboss.org/browse/SWSQE-296 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > Kiali Deploy job failing, with or without REMOVE_KIALI enabled: > Undeploy Kiali on Openshift > the server doesn't have a resource type "routerules" > make: *** [openshift-undeploy] Error 1 > Ex: [http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-296) Kiali-on-Openshift Failing

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-296?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-296: -------------------------------------- I have updated the description on http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshift/. It was a bug, and was fixed in a script change. > Kiali-on-Openshift Failing > -------------------------- > > Key: SWSQE-296 > URL: https://issues.jboss.org/browse/SWSQE-296 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > Kiali Deploy job failing, with or without REMOVE_KIALI enabled: > Undeploy Kiali on Openshift > the server doesn't have a resource type "routerules" > make: *** [openshift-undeploy] Error 1 > Ex: [http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3927) Bump logging subsystem schema and model version

by James Perkins (JIRA)

James Perkins created WFCORE-3927: ------------------------------------- Summary: Bump logging subsystem schema and model version Key: WFCORE-3927 URL: https://issues.jboss.org/browse/WFCORE-3927 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Move the model to 7.0.0 and the schema to 6.0. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2625) Executable model - AccumulateTest and other tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2625?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2625: ------------------------------------- 2nd fix https://github.com/kiegroup/drools/commit/bbe48b9597c8f888032c5b044e7fdfe... > Executable model - AccumulateTest and other tests fail with the model > --------------------------------------------------------------------- > > Key: DROOLS-2625 > URL: https://issues.jboss.org/browse/DROOLS-2625 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: > - AccumulateTest > - AlphaNetworkModifyTest > - AlphaTest > - AnnotationsTest > - ArrayTest > - BackwardChainingTest > PR with tests: https://github.com/kiegroup/drools/pull/1941 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2532: ------------------------------------- [~danielezonca] Updated demo and pdf with live search field for DO's, based on feedback. Need to talk with Matthew about the behavior but I think it could pickup something that's already in the workbench where the search terms dynamically update the items below (rather than adding a dropdown to the field.) tbd. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: Proposed.pdf, Proposed_2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1602) Temporarily add a Pem.generatePemX509Certificate() method that takes the ByteStringBuilder from Elytron as a parameter

by Farah Juma (JIRA)

Farah Juma created ELY-1602: ------------------------------- Summary: Temporarily add a Pem.generatePemX509Certificate() method that takes the ByteStringBuilder from Elytron as a parameter Key: ELY-1602 URL: https://issues.jboss.org/browse/ELY-1602 Project: WildFly Elytron Issue Type: Task Components: Utils Reporter: Farah Juma Assignee: Farah Juma As discussed with Martin and Darran, temporarily add a {{Pem.generatePemX509Certificate()}} method that takes the {{ByteStringBuilder}} from Elytron as a parameter. This will prevent the need for [modifying|https://github.com/wildfly/wildfly-core/pull/3316#issuecomment-...] {{org.wildfly.extension.elytron.AdvancedModifiableKeyStoreDecorator}} when building Core with the latest Elytron SNAPSHOT version. Since {{org.wildfly.security.pem.Pem}} is private API, we can remove this new method later on. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: Proposed_2.pdf > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: Proposed.pdf, Proposed_2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-296) Kiali-on-Openshift Failing

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-296?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-296: ------------------------------------ I added to the REMOVE_KIALI description in the main job - we can close this issue if you are comfortable with this not being an issue. > Kiali-on-Openshift Failing > -------------------------- > > Key: SWSQE-296 > URL: https://issues.jboss.org/browse/SWSQE-296 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > Kiali Deploy job failing, with or without REMOVE_KIALI enabled: > Undeploy Kiali on Openshift > the server doesn't have a resource type "routerules" > make: *** [openshift-undeploy] Error 1 > Ex: [http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10571) Exclusion groupId and artifactId in the wrong order in the root pom

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10571?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10571: ---------------------------------- Priority: Trivial (was: Major) > Exclusion groupId and artifactId in the wrong order in the root pom > ------------------------------------------------------------------- > > Key: WFLY-10571 > URL: https://issues.jboss.org/browse/WFLY-10571 > Project: WildFly > Issue Type: Task > Components: Build System > Affects Versions: 13.0.0.Final > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Trivial > > e.g. in https://github.com/wildfly/wildfly/blob/13.0.0.Final/pom.xml#L4198 the exclusions have groupId and artifactId in the wrong order. e.g. > {code} > <exclusion> > <artifactId>hal-ballroom</artifactId> > <groupId>org.jboss.hal</groupId> > </exclusion> > {code} > should be > {code} > <exclusion> > <groupId>org.jboss.hal</groupId> > <artifactId>hal-ballroom</artifactId> > </exclusion> > {code} > While the former is valid, it is confusing, and seems to have been introduced in the refactoring to use the component-matrix (which was later undone) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10571) Exclusion groupId and artifactId in the wrong order in the root pom

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10571?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10571: ---------------------------------- Issue Type: Task (was: Feature Request) > Exclusion groupId and artifactId in the wrong order in the root pom > ------------------------------------------------------------------- > > Key: WFLY-10571 > URL: https://issues.jboss.org/browse/WFLY-10571 > Project: WildFly > Issue Type: Task > Components: Build System > Affects Versions: 13.0.0.Final > Reporter: Kabir Khan > Assignee: Kabir Khan > > e.g. in https://github.com/wildfly/wildfly/blob/13.0.0.Final/pom.xml#L4198 the exclusions have groupId and artifactId in the wrong order. e.g. > {code} > <exclusion> > <artifactId>hal-ballroom</artifactId> > <groupId>org.jboss.hal</groupId> > </exclusion> > {code} > should be > {code} > <exclusion> > <groupId>org.jboss.hal</groupId> > <artifactId>hal-ballroom</artifactId> > </exclusion> > {code} > While the former is valid, it is confusing, and seems to have been introduced in the refactoring to use the component-matrix (which was later undone) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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