There are currently two COMPOSE_ID files on the primary which help MirrorManager to detect if the content on the primary has changed.
COMPOSE_ID
Unfortunately it still can happen that MirrorManager scans the primary mirror while either 9-stream/ or SIGs/ is being updated. This can lead to wrong results on the MirrorManager side which are not always automatically recoverable.
9-stream/
SIGs/
Would it be possible to have files, next to both COMPOSE_ID, which marks that the primary mirror is currently being updated. Maybe COMPOSE_ID.lock or .sync_in_progress.
COMPOSE_ID.lock
.sync_in_progress
Just something which helps MirrorManager to not scan the primary mirror while the content is being updated.
Metadata Update from @arrfab: - Issue tagged with: centos-stream, feature-request, high-gain, high-trouble
Hi @adrian,
thanks for reporting this but, this seems to be a flaw in the design of the mirror manager. It might be a good idea to write a CPE initiative to help with the maintenance and development of the mirror manager. https://pagure.io/cpe/initiatives-proposal
Metadata Update from @humaton: - Issue untagged with: centos-stream, feature-request, high-gain, high-trouble - Issue close_status updated to: To resubmit as CPE initiative - Issue status updated to: Closed (was: Open)
I opened a PR at https://github.com/CentOS/ansible-role-stylo/pull/2
Log in to comment on this ticket.