Issue:

Creating a custom repo on Satellite 6.15 also creates a record for the repo in the `cp2_content` table of the Candlepin database. After upgrading to Satellite 6.16 and deleting the custom repo, the record in the `cp2_content` table remains present. Attempting to delete organization that contained the repo after the repo has been deleted fails due to a lock created by the `cp2_content` record.

Steps to test:

1. Deploy Satellite 6.15.

2. Create a new organization.

3. Create a custom product in the new organization.

4. Create a custom yum repo in the custom product.

4. Upgrade the Satellite to 6.16.

5. Delete the custom repo.

6. Attempt to delete the new organization.

Expected Results:

Organization can be successfully deleted.

Actual Results:

Attempting to delete the organization fails with the following entry in /var/log/candlepin/error.log: `ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - ERROR: update or delete on table "cp_owner" violates foreign key constraint "cp2_owner_content_fk1" on table "cp2_owner_content"

Detail: Key (id)=(XXXXXXXXXX) is still referenced from table "cp2_owner_content".`