pulp db migrations are not meant to be run while pulp processes are active and can cause major data issues if there are active workers. There should be a test to prevent this at the startup of the pulp-manage-db process. This can result in duplicate entries and errors trying to migrate data. See this KCS for errors caused by this: [Satellite 6.2] pulp raises E11000 duplicate key error index: pulp_database.units_ostree.$remote_id_1_branch_1_commit_1 https://access.redhat.com/solutions/2534911
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
This is a duplicate of 1374723. They both are associated with the same upstream Pulp issue also. *** This bug has been marked as a duplicate of bug 1374723 ***
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days