Fixes #36871 - Fix incremental update concurrency #10781
Conversation
m-bucher
force-pushed
the
disable_incr_update_concurrency_in_cv
branch
from
0a7aeda to
78b2a98
Compare
Do not run Incremental Updates on the same Content View in parallel
m-bucher
force-pushed
the
disable_incr_update_concurrency_in_cv
branch
from
78b2a98 to
776e08c
Compare
|
Tested on Katello 4.7 and seems to be working fine. Tested with normal CVs and composite CVs. Going to test now on the latest code. |
There was a problem hiding this comment.
Working fine for me! Tested again on the latest Katello code. Created a CV with two versions that contain the same repo with different content. The content difference was created via RPM deletion in the UI. Each content view version has a different LCE.
I subscribed one host to each LCE and ensured that each had one applicable erratum to apply. I then ran the incremental update via the UI. The incremental update generate two new content view versions, each had the appropriate content in it. I also confirmed that applying the new content to the host after incremental update still works.
Do not run Incremental Updates on the same Content View in parallel