September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-422) Fix failing graph layout test

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-422: ------------------------------------ Summary: Fix failing graph layout test Key: SWSQE-422 URL: https://issues.jboss.org/browse/SWSQE-422 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2996) Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final

by Prameela Pod (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2996?page=com.atlassian.jira.plugi... ] Prameela Pod updated DROOLS-2996: --------------------------------- Steps to Reproduce: Extract the zip file Import project into workspace Run the class(DroolsTest.java - Run as java application) verify the console logs FYI.. Please find the test case results log files attached in JIRA was: Extract the zip file Import proect into workspace Run the class(DroolsTest.java - Run as java application) verify the console logs FYI.. Please find the test case results log files attached in JIRA > Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2996 > URL: https://issues.jboss.org/browse/DROOLS-2996 > Project: Drools > Issue Type: Bug > Affects Versions: 7.4.1.Final > Reporter: Prameela Pod > Assignee: Mario Fusco > Attachments: DroolsTestPortlet.zip, logs.txt > > > After drools migration from 6.0.3 to 7.4.1.Final version , modify property in 1st rule not validating conditions in 2nd rule. > Ex: modify($alarm){setEVENTO_EN_TAREA("YES")} - In 1st rule then condition > $alarm: ALARMA_ERICSSON_2G("NO" == getEVENTO_EN_TAREA()) - When condition in 2nd rule. > If getEVENTO_EN_TAREA() = "YES" then only it should go inside 2nd rule.But here in this case getEVENTO_EN_TAREA()="YES" or "NO" - For both cases 2nd rule when condition is matched and going inside then condition.Which is wrong > Please find the attached sample test project with logs. > Kindly let me know additional information is required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-384) Add Automation tests for Applications

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-384?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-384. ---------------------------------- Resolution: Done PR merged > Add Automation tests for Applications > ------------------------------------- > > Key: SWSQE-384 > URL: https://issues.jboss.org/browse/SWSQE-384 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-384) Add Automation tests for Applications

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-384?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-384: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/74 > Add Automation tests for Applications > ------------------------------------- > > Key: SWSQE-384 > URL: https://issues.jboss.org/browse/SWSQE-384 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2996) Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final

by Prameela Pod (JIRA)

Prameela Pod created DROOLS-2996: ------------------------------------ Summary: Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final Key: DROOLS-2996 URL: https://issues.jboss.org/browse/DROOLS-2996 Project: Drools Issue Type: Bug Affects Versions: 7.4.1.Final Reporter: Prameela Pod Assignee: Mario Fusco Attachments: DroolsTestPortlet.zip, logs.txt After drools migration from 6.0.3 to 7.4.1.Final version , modify property in 1st rule not validating conditions in 2nd rule. Ex: modify($alarm){setEVENTO_EN_TAREA("YES")} - In 1st rule then condition $alarm: ALARMA_ERICSSON_2G("NO" == getEVENTO_EN_TAREA()) - When condition in 2nd rule. If getEVENTO_EN_TAREA() = "YES" then only it should go inside 2nd rule.But here in this case getEVENTO_EN_TAREA()="YES" or "NO" - For both cases 2nd rule when condition is matched and going inside then condition.Which is wrong Please find the attached sample test project with logs. Kindly let me know additional information is required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1668) LDAP searchScope=OBJECT_SCOPE Elytron alternative

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1668?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1668: --------------------------------------- Just bumped to Critical so hopefully we can at least triage the issue. > LDAP searchScope=OBJECT_SCOPE Elytron alternative > ------------------------------------------------- > > Key: ELY-1668 > URL: https://issues.jboss.org/browse/ELY-1668 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.6.1.Final > Reporter: Martin Choma > Priority: Critical > Fix For: 1.7.0.CR1 > > > During comparing PicketBox an Elytron we came to one scenario which I am not sure if is covered by Elytron. > "As a user I am able to authenticate and authorize into web application secured by LDAP (where the same is used for storing identities and roles) and roles are stored in tree structure and should be only referenced object." Author is Ondra Lukas which is not with us anymore so I tried to think about what could this be about? Based on context I came to conclusion this is about OBJECT_SCOPE value of property searchScope. > Could you revise if same is possible with Elytron? But anyway I am not sure how that feature can be useful. But maybe there is some corner case it can be useful I am not aware of. > {code} > dn: ou=People,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: People > dn: uid=jduke,ou=People,${dnSuffix} > objectclass: top > objectclass: person > objectclass: inetOrgPerson > uid: jduke > cn: Java Duke > sn: Duke > userPassword: Password1 > dn: ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: RolesLevel1 > dn: cn=RoleUnderLevel1,ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: groupOfNames > cn: RoleUnderLevel1 > member: uid=jduke,ou=People,${dnSuffix} > description: the RoleUnderLevel1 group > {code} > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1668) LDAP searchScope=OBJECT_SCOPE Elytron alternative

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1668?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1668: ---------------------------------- Fix Version/s: 1.7.0.CR1 > LDAP searchScope=OBJECT_SCOPE Elytron alternative > ------------------------------------------------- > > Key: ELY-1668 > URL: https://issues.jboss.org/browse/ELY-1668 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.6.1.Final > Reporter: Martin Choma > Fix For: 1.7.0.CR1 > > > During comparing PicketBox an Elytron we came to one scenario which I am not sure if is covered by Elytron. > "As a user I am able to authenticate and authorize into web application secured by LDAP (where the same is used for storing identities and roles) and roles are stored in tree structure and should be only referenced object." Author is Ondra Lukas which is not with us anymore so I tried to think about what could this be about? Based on context I came to conclusion this is about OBJECT_SCOPE value of property searchScope. > Could you revise if same is possible with Elytron? But anyway I am not sure how that feature can be useful. But maybe there is some corner case it can be useful I am not aware of. > {code} > dn: ou=People,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: People > dn: uid=jduke,ou=People,${dnSuffix} > objectclass: top > objectclass: person > objectclass: inetOrgPerson > uid: jduke > cn: Java Duke > sn: Duke > userPassword: Password1 > dn: ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: RolesLevel1 > dn: cn=RoleUnderLevel1,ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: groupOfNames > cn: RoleUnderLevel1 > member: uid=jduke,ou=People,${dnSuffix} > description: the RoleUnderLevel1 group > {code} > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1668) LDAP searchScope=OBJECT_SCOPE Elytron alternative

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1668?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1668: ---------------------------------- Priority: Critical (was: Major) > LDAP searchScope=OBJECT_SCOPE Elytron alternative > ------------------------------------------------- > > Key: ELY-1668 > URL: https://issues.jboss.org/browse/ELY-1668 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.6.1.Final > Reporter: Martin Choma > Priority: Critical > Fix For: 1.7.0.CR1 > > > During comparing PicketBox an Elytron we came to one scenario which I am not sure if is covered by Elytron. > "As a user I am able to authenticate and authorize into web application secured by LDAP (where the same is used for storing identities and roles) and roles are stored in tree structure and should be only referenced object." Author is Ondra Lukas which is not with us anymore so I tried to think about what could this be about? Based on context I came to conclusion this is about OBJECT_SCOPE value of property searchScope. > Could you revise if same is possible with Elytron? But anyway I am not sure how that feature can be useful. But maybe there is some corner case it can be useful I am not aware of. > {code} > dn: ou=People,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: People > dn: uid=jduke,ou=People,${dnSuffix} > objectclass: top > objectclass: person > objectclass: inetOrgPerson > uid: jduke > cn: Java Duke > sn: Duke > userPassword: Password1 > dn: ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: organizationalUnit > ou: RolesLevel1 > dn: cn=RoleUnderLevel1,ou=RolesLevel1,${dnSuffix} > objectclass: top > objectclass: groupOfNames > cn: RoleUnderLevel1 > member: uid=jduke,ou=People,${dnSuffix} > description: the RoleUnderLevel1 group > {code} > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2292) Prevent DNS_PING from adding suffix dynamically

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created JGRP-2292: ----------------------------------------- Summary: Prevent DNS_PING from adding suffix dynamically Key: JGRP-2292 URL: https://issues.jboss.org/browse/JGRP-2292 Project: JGroups Issue Type: Enhancement Reporter: Sebastian Łaskawiec Assignee: Bela Ban The {{DNS_PING}} can also be used in different environments than Kubernetes and OpenShift. However, it adds an {{svc.local}} prefix to all queries, which makes it very hard (or impossible) to use it for different things than Kube. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2292) Prevent DNS_PING from adding suffix dynamically

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/JGRP-2292?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned JGRP-2292: ----------------------------------------- Assignee: Sebastian Łaskawiec (was: Bela Ban) > Prevent DNS_PING from adding suffix dynamically > ----------------------------------------------- > > Key: JGRP-2292 > URL: https://issues.jboss.org/browse/JGRP-2292 > Project: JGroups > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > The {{DNS_PING}} can also be used in different environments than Kubernetes and OpenShift. However, it adds an {{svc.local}} prefix to all queries, which makes it very hard (or impossible) to use it for different things than Kube. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018