*** Bug 1656612 has been marked as a duplicate of this bug. ***
will a fix of this candlepin BZ include also scenario when deleting a Sat product? That invokes many Actions::Candlepin::Product::ContentRemove dynflow steps concurrently, i.e. many requests like:
Request: verb=DELETE, uri=/candlepin/owners/RedHat/products/73563395718/content/1561805575836
for the same product but different content are raised concurrently.
Will this BZ fix prevent the "Runtime Error Row was updated or deleted by another transaction" error I see in Sat6.5? (cf https://bugzilla.redhat.com/show_bug.cgi?id=1609543#c22)
For the creation of content there is a batch endpoint:
Feels like we need a batch delete as well.
There is no good way to allow concurrent adds/deletes of content for the same product. The locking would be extensive an obtrusive.