Description of problem:

Error creating resources populated using scripts containing hard coded IDs. The actual error is a 409 (conflict).  Reported by folks preparing for RH Summit workshops.  They populate the inventory using the Tackle CLI and .yaml files defining REST resources having the ID fields set.

Version-Release number of selected component (if applicable):

7.2  

How reproducible:

Always 

Steps to Reproduce:
1. Start with a fresh install.
2. Using curl or a script, create a resource such as an application with ID=1.
3. Using the UI, try to create an application.

Actual results:

 Fails with underlying http 409.

Expected results:

No error. 

Additional info: