Description of problem:

Deleting the existing manifest and importing a new manifest ends in a below warning state.

PG::ForeignKeyViolation: ERROR: update or delete on table "katello_pools" violates foreign key constraint "katello_pool_products_pool_id_fk" on table "katello_pool_products" DETAIL: Key (id)=(27) is still referenced from table "katello_pool_products".

How reproducible:

100%

Is this issue a regression from an earlier version:

Steps to Reproduce:

1. delete existing manifest

2. create new manifest on custoemr portal

3. importing new manifest

Actual behavior:

importing new manifest task ended in a warning state

PG::ForeignKeyViolation: ERROR: update or delete on table "katello_pools" violates foreign key constraint "katello_pool_products_pool_id_fk" on table "katello_pool_products" DETAIL: Key (id)=(27) is still referenced from table "katello_pool_products".

Expected behavior:
Tasks should be completed successfully without any errors or warning

Business Impact / Additional info: