From 8cfb7c9f995e346c9f1850a9b7bd9126882f7282 Mon Sep 17 00:00:00 2001 From: mprahl Date: Thu, 28 Feb 2019 14:41:45 -0500 Subject: [PATCH] Add a log statement to know when the poller processes a paused module build We encountered an issue where start_next_batch_build was called twice on a module build and it caused the module build to fail because Brew failed one of the components since it was submitted twice. This will help us narrow down the issue if it happens again. --- module_build_service/scheduler/producer.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/module_build_service/scheduler/producer.py b/module_build_service/scheduler/producer.py index 6df26cc5..339ea934 100644 --- a/module_build_service/scheduler/producer.py +++ b/module_build_service/scheduler/producer.py @@ -231,6 +231,7 @@ class MBSProducer(PollingProducer): log.warning('process_open_component_builds is not yet implemented...') def process_paused_module_builds(self, config, session): + log.info('Looking for paused module builds in the build state') if module_build_service.utils.at_concurrent_component_threshold( config, session): log.debug('Will not attempt to start paused module builds due to ' @@ -255,6 +256,7 @@ class MBSProducer(PollingProducer): # repo-regen. if (not module_build.current_batch(koji.BUILD_STATES['BUILDING']) and not module_build.new_repo_task_id): + log.info(' Processing the paused module build %r', module_build) # Initialize the builder... builder = GenericBuilder.create_from_module( session, module_build, config)