Hide Forgot
Description of problem: A catalog is the grouping of catalog entries, there should be no need to have unique catalog entry names across all catalogs. For instance, if I have two catalogs {Catalog A, Catalog B} and Catalog A has a Catalog Entry named 'foo', I should be able to drill down into Catalog B and create a Catalog Entry named 'foo'. The unique name check should not be check across all catalogs. Version-Release number of selected component (if applicable): How reproducible: Create a catalog A. In catalog A, create a catalog entry called 'foo'. Create a catalog B. In catalog B, try to create a catalog entry called 'foo'. You will see that the name is not allowed because it's 'not available'. This is because an entry with that name exists in Catalog A. Actual results: Catalog entry names are checked for uniqueness across catalogs Expected results: Catalog entry names should be checked for uniqueness within a catalog only Additional info:
commit 8fb47ddcfa2adafc814c7f0fcf861a1124bbb54b conductor.git repo
wrong commit, still posted.
commit 80caf4fc48f6eac6ac85d34d5bbf474e1f02dc72 conductor.git repo
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html