Bug 1072337

Summary:	DS is created after testing connection failure in domain
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jakub Cechacek <jcechace>
Component:	Web Console	Assignee:	Harald Pehl <hpehl>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jakub Cechacek <jcechace>
Severity:	high	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	brian.stansberry, hbraun, hpehl, jkudrnac, kkhan, rhatlapa, rsvoboda, smumford
Target Milestone:	DR4
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-28 15:44:39 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:	1072962
Bug Blocks:	1051640

Description Jakub Cechacek 2014-03-04 12:09:07 UTC

Testing connection to invalid configuration will cause DS to be created in DS creation wizard in domain

Steps to Reproduce:
1. Start EAP 6.3 domain, open Web Console, navigate to datasources
2. Go through wizard steps (use invalid configuration) on step 3 hit "Test Connection" 
3. a) click done 
   b) click cancel  

Actual results:
   a) an error messages informing about already existing DS
   b) after reload DS is created anyway

Expected results:
   a) DS should be created only AFTER the wizard is finished 
   b) DS should not be created

Comment 1 Rostislav Svoboda 2014-03-04 12:40:23 UTC

Setting blocker? flag as it's needed to fix this BZ for https://issues.jboss.org/browse/EAP6-66

Comment 2 Jakub Cechacek 2014-03-05 11:32:19 UTC

AFAIK the "Test Connection" feature creates a temporary DS which is configured in the exactly same configuration as entered in wizard (same name, jndi, etc..) and not remove afterwards.

This can be verified through CLI after using the "Test Connection" functionality in the wizard.

Comment 3 Harald Pehl 2014-03-05 13:57:23 UTC

Caused by a wrong recovery from a management operation

Comment 4 Jakub Cechacek 2014-03-21 11:14:11 UTC

This is most likely fixed (I haven't noticed this issue in DR4). Not sure why it didn't reach QA. Requesting info from Harald.

Comment 5 Harald Pehl 2014-03-21 11:21:41 UTC

Yes this was fixed as part of 1072962. Please remove beta blocker.

Comment 6 Kabir Khan 2014-04-02 17:17:27 UTC

Fixed for console upgrade in DR4

Comment 7 Jakub Cechacek 2014-04-03 07:13:02 UTC

Verified as per comments above.

Comment 8 Scott Mumford 2014-05-14 00:53:36 UTC

Marking for exclusion from 6.3.0 Beta release notes as both 'affects' and 'fix' versions are listed as 6.3.0, suggesting this was not a customer-facing issue.

Comment 9 JBoss JIRA Server 2015-04-28 15:08:57 UTC

John Doyle <jdoyle> updated the status of jira EAP6-66 to Closed