Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1132297

Summary: [QE] (6.3.0) Intermittent fail of org.jboss.as.test.integration.domain.web.DomainClusteredSSOTestCase#testSso
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: TestsuiteAssignee: Chao Wang <chaowan>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: cdewolf, istudens, jason.greene, jawilson, ozizka, pkremens
Target Milestone: CR1   
Target Release: EAP 6.4.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 10:34:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 996500, 1231259    
Attachments:
Description Flags
DomainClusteredSSOTestCase none

Description Petr Kremensky 2014-08-21 06:06:51 UTC
Created attachment 929029 [details]
DomainClusteredSSOTestCase

Description of problem:
 testSso() fails quite often if testsuite run is properly configured (don't use localhost for node0 and node1).
 
Version-Release number of selected component (if applicable):
 6.3.0

How reproducible:
 Always

Steps to Reproduce:
 1. unzip jboss-eap-6.3.0-testsuite-local-repository.zip into $REPO directory
 2. ./build.sh -Dmaven.repo.local=$REPO -DskipTests
 3. ./integration-tests.sh -Dts.noSmoke -Dmaven.repo.local=$REPO -Dts.domain -Dtest=org.jboss.as.test.integration.domain.web.DomainClusteredSSOTestCase -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2

Actual results:
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.jboss.as.test.integration.domain.web.DomainClusteredSSOTestCase
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 42.365 sec <<< FAILURE!

Results :

Failed tests:   testSso(org.jboss.as.test.integration.domain.web.DomainClusteredSSOTestCase): Server-Two Unexpected HTTP response status code. expected:<200> but was:<401>

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0


Expected results:
Test always pass.

Additional info:

Comment 1 Petr Kremensky 2014-08-21 06:41:07 UTC
Test sometimes fails also on different places:
ava.lang.AssertionError: Server-One Unexpected HTTP response status code. expected:<401> but was:<400>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:743)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:555)
	at org.jboss.as.test.integration.domain.web.DomainClusteredSSOTestCase.testSso(DomainClusteredSSOTestCase.java:161)
        ...

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6.3.x-testsuite-nodes-RHEL/jdk=java17_default,label_exp=vmg19-rhel5-x86/5/testReport/org.jboss.as.test.integration.domain.web/DomainClusteredSSOTestCase/testSso/

Comment 6 Petr Kremensky 2015-07-03 04:56:02 UTC
PR affects only testsuite, no changes in EAP codebase.

https://github.com/jbossas/jboss-eap/pull/2471

Comment 9 Petr Kremensky 2015-07-31 12:36:11 UTC
Verified on EAP 6.4.3.CP.CR1

Comment 10 Petr Penicka 2017-01-17 10:34:57 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.