I get a lot of errors like this every single time I try to delete an unused
content view.
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error null at
org.candlepin.model.AbstractHibernateCurator.delete:326
Runtime Error Batch update returned unexpected row count from update [0];
actual row count: 0; expected: 1 at
org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched:81
It doesn't matter what view I'm deleting (regular or composite) it always
happens.
If I go into the dynflow console and just keep hitting resume 9 or 10 times
it will eventually finish.
I would prefer to not have to babysit this process though.
Why is this happening and do you guys have a bug fix for this consistently
bad behavior?