February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-9) Select UI Automation Framework

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-9?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney updated SWSQE-9: ----------------------------- Team: Infrastructure > Select UI Automation Framework > ------------------------------ > > Key: SWSQE-9 > URL: https://issues.jboss.org/browse/SWSQE-9 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Team Infrastructure Task - *Team decision out framework selection* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-6781. ---------------------------- Resolution: Out of Date > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Jeff Mesnil > Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log > > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-21) Openshift Source-2-Image Pipeline for Test Suites

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-21?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-21: ------------------------------ Team: Infrastructure > Openshift Source-2-Image Pipeline for Test Suites > ------------------------------------------------- > > Key: SWSQE-21 > URL: https://issues.jboss.org/browse/SWSQE-21 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: viet nguyen > > Configure an Openshift Source-to-Image pipline for QE test suites. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-14) Python Selenium Prototype with SWS UI

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-14?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-14: ------------------------------ Team: Infrastructure > Python Selenium Prototype with SWS UI > ------------------------------------- > > Key: SWSQE-14 > URL: https://issues.jboss.org/browse/SWSQE-14 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Verify that Python Selenium automation work with SWS UI (i.e. React.js) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-6) React.js Prototype

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-6?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney updated SWSQE-6: ----------------------------- Team: Infrastructure > React.js Prototype > ------------------ > > Key: SWSQE-6 > URL: https://issues.jboss.org/browse/SWSQE-6 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: viet nguyen > > Github: https://github.com/Hawkular-QE/swsui-test > Travis-ci: https://travis-ci.org/Hawkular-QE/swsui-test -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-16) Set Up Confluence Board

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-16?page=com.atlassian.jira.plugin.s... ] Matt Mahoney updated SWSQE-16: ------------------------------ Team: Infrastructure > Set Up Confluence Board > ----------------------- > > Key: SWSQE-16 > URL: https://issues.jboss.org/browse/SWSQE-16 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Prachi Yadav > Priority: Minor > > * We could have meeting notes, sprint retrospective notes, we could reference JIRAs (QE and Dev board), create pages for tasks documentation even test plans could be created on Confluence -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-31) QE Git Repository for SWS

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-31?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo commented on SWSQE-31: ---------------------------------------------- We have Hawkular QE repository (hawkular-qe-utils) Should we move to another repository for SWS? > QE Git Repository for SWS > -------------------------- > > Key: SWSQE-31 > URL: https://issues.jboss.org/browse/SWSQE-31 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1519) Make restore of SecurityIdentity on replicated session configurable

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1519?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1519: ------------------------------ Steps to Reproduce: clones of testNodeRestart, testFailover, testChangeNode from SPNEGOSessionManualHaTest using new flag {code} git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/tests-ldap-kerberos.git ./build-eap71.sh -Deap -Dversion.jboss.bom=7.2.0.EL12.Beta1 -Dversion.wildfly.core=4.0.0.Beta1-redhat-1 -Dmaven.repo.local=/home/mchoma/eap/7.2.0.EL12.ER1/jboss-eap-7.2.0.EL12.Beta1-maven-repository/maven-repository -Djboss.dist=/home/mchoma/eap/7.2.0.EL12.ER1/jboss-eap-7.2 -Dtest=SPNEGOSessionManualHaTest {code} was: clones of testNodeRestart, testFailover, testChangeNode from SPNEGOSessionManualHaTest using new flag /code git clone git@gitlab.mw.lab.eng.bos.redhat.com:mchoma/tests-ldap-kerberos.git ./build-eap71.sh -Deap -Dversion.jboss.bom=7.2.0.EL12.Beta1 -Dversion.wildfly.core=4.0.0.Beta1-redhat-1 -Dmaven.repo.local=/home/mchoma/eap/7.2.0.EL12.ER1/jboss-eap-7.2.0.EL12.Beta1-maven-repository/maven-repository -Djboss.dist=/home/mchoma/eap/7.2.0.EL12.ER1/jboss-eap-7.2 -Dtest=SPNEGOSessionManualHaTest > Make restore of SecurityIdentity on replicated session configurable > ------------------------------------------------------------------- > > Key: ELY-1519 > URL: https://issues.jboss.org/browse/ELY-1519 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Final > Reporter: Martin Choma > > Currently in clustered environment Security Identity is restored during > * failover > * load balancer change node (not sticky behaviour) > * session passivation/activation > This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. > So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. > This is follow up on ELY-1503 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1519) Make restore of SecurityIdentity on replicated session configurable

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1519?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1519: ------------------------------ Description: Currently in clustered environment Security Identity is restored during * failover * load balancer change node (not sticky behaviour) * session passivation/activation This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. was: Currently in clustered environment Security Identity is restored during * failover * load balancer change node (not sticky behaviour) * session passivation/activation This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. This is follow up on ELY-1503 > Make restore of SecurityIdentity on replicated session configurable > ------------------------------------------------------------------- > > Key: ELY-1519 > URL: https://issues.jboss.org/browse/ELY-1519 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Final > Reporter: Martin Choma > > Currently in clustered environment Security Identity is restored during > * failover > * load balancer change node (not sticky behaviour) > * session passivation/activation > This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. > So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1519) Make restore of SecurityIdentity on replicated session configurable

by Martin Choma (JIRA)

Martin Choma created ELY-1519: --------------------------------- Summary: Make restore of SecurityIdentity on replicated session configurable Key: ELY-1519 URL: https://issues.jboss.org/browse/ELY-1519 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms Affects Versions: 1.2.0.Final Reporter: Martin Choma Currently in clustered environment Security Identity is restored during * failover * load balancer change node (not sticky behaviour) * session passivation/activation This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. This is follow up on ELY-1503 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018