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

Bug 1270336

Summary: Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Van Halbert <vhalbert>
Component: Teiid, Tooling, IntegrationAssignee: jolee
Status: CLOSED WONTFIX QA Contact: Jan Stastny <jstastny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: drieden, jstastny, vhalbert
Target Milestone: GA   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
If you try to deploy a virtual database after a dynamic virtual database with exactly the same name has already been deployed, it will fail. To work around this problem, avoid mixing VDB types.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-07 14:17:40 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:

Comment 2 JBoss JIRA Server 2015-10-12 14:11:44 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3747 to Resolved

Comment 4 JBoss JIRA Server 2016-01-27 21:25:04 UTC
Steven Hawkins <shawkins> updated the status of jira TEIID-3747 to Closed

Comment 8 David Le Sage 2017-05-11 03:33:48 UTC
I have amended the release note to indicate that they both have exactly the same name.