Red Hat Bugzilla – Bug 823451
force template name/UUID uniqueness on DC level, not at whole setup level
Last modified: 2015-09-22 09:09 EDT
Description of problem:
force template name uniqueness on DC level, not setup level. Current behavior prevents admin to use identical template in two data centers of the same RHEV-M setup.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have a RHEV-M setup with two data centers and with a template in an export domain
2. import a template to first data center
3. try to import the template to second data center
import of a template fails with "Import Template Failed - Template Id already exist in the system. Please remove the Template ($TEMPLATE_NAME) from the system first."
*** This bug has been marked as a duplicate of bug 567580 ***