Bug 1105003 - (6.4.z) [QE] org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.testRightVaultPassword fails mainly on Solaris SPARC due to unexpected logs in CLI output
Summary: (6.4.z) [QE] org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLIT...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: CR2
: EAP 6.4.1
Assignee: Petr Kremensky
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks: eap641-payload
TreeView+ depends on / blocked
 
Reported: 2014-06-05 08:00 UTC by Pavel Jelinek
Modified: 2017-01-17 09:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Solaris SPARC
Last Closed: 2017-01-17 09:57:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
standard output (7.55 KB, application/zip)
2014-06-05 08:00 UTC, Pavel Jelinek
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBQA-10097 0 Major Open [QE] (6.3.0) org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.testRightVaultPassword fails mainly... 2017-09-25 13:41:20 UTC
Red Hat Issue Tracker WFLY-3778 0 Major Resolved Tests in Manualmode test suite fail occasionally 2017-09-25 13:41:20 UTC

Description Pavel Jelinek 2014-06-05 08:00:14 UTC
Created attachment 902440 [details]
standard output

See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-6x-as-testsuite-Solaris-matrix-OracleJDK6/141/BITS=-d64,jdk=java16_default,label_exp=solaris11%26%26sparc/testReport/org.jboss.as.test.manualmode.management.cli/VaultPasswordsInCLITestCase/testRightVaultPassword/

Stacktrace:
java.lang.AssertionError: Password should be right and authentication successful
Expected: a string containing "\"outcome\" => \"success\""
     but: was "0: INFO  [org.jboss.modules] JBoss Modules version 1.3.3.Final-redhat-1
INFO  [org.jboss.security] PBOX000361: Default Security Vault Implementation Initialized and Ready
INFO  [org.xnio] XNIO Version 3.0.9.GA-redhat-1
INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.9.GA-redhat-1
INFO  [org.jboss.remoting] JBoss Remoting version (unknown)
"
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:865)
	at org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.testRightVaultPassword(VaultPasswordsInCLITestCase.java:153)

Comment 1 Pavel Jelinek 2014-07-23 11:54:38 UTC
At the beggining of this issue there is inability of prepareServer() method to reload server using CustomCLIExecutor.

Comment 6 Petr Kremensky 2015-04-02 12:10:01 UTC
This one is caused by hard coded 5 sec timeout in CustomCLIExecutor which is not enough (in our testing environment).

private static final int CLI_PROC_TIMEOUT = 5000;
...
if (runningTime >= CLI_PROC_TIMEOUT) {
    readStream(cliOutBuf, cliStream);
    cliProc.destroy();
    wait = false;
}

this causes the failures like as management operation didn't finish by the time:
java.lang.AssertionError: Password should be right and authentication successful
Expected: a string containing "\"outcome\" => \"success\""
     but: was "0: INFO  [org.jboss.modules] JBoss Modules version 1.3.6.Final-redhat-1
INFO  [org.jboss.security] PBOX000361: Default Security Vault Implementation Initialized and Ready
INFO  [org.xnio] XNIO Version 3.0.13.GA-redhat-1
INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.13.GA-redhat-1
INFO  [org.jboss.remoting] JBoss Remoting version 3.3.4.Final-redhat-1
"
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:865)
	at org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.testRightVaultPassword(VaultPasswordsInCLITestCase.java:153)

Increasing the timeout and adding --timeout to command should solve this.

Comment 8 Petr Kremensky 2015-04-03 07:38:32 UTC
This one should solve BZ1105003

Comment 9 Petr Kremensky 2015-04-03 07:39:08 UTC
^^ BZ1136220

Comment 10 Rostislav Svoboda 2015-04-23 11:50:57 UTC
Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup.

Comment 12 Petr Kremensky 2015-05-18 07:57:02 UTC
Verified on EAP 6.4.1.CP.CR2

Comment 13 JBoss JIRA Server 2015-11-26 14:27:17 UTC
Tomaz Cerar <tomaz.cerar> updated the status of jira WFLY-3778 to Resolved

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


Note You need to log in before you can comment on or make changes to this bug.