This issue was reported in bug 1752075
info: Getting tag for hedgewars:master:3020190917180335 info: Start to handle hedgewars:master:3020190917180335:f1d02342 which is in init state. info: Finding the default modules to include as buildrequires info: The base module platform:f30:6:00000000 has no default modules info: Setting build arches of hedgewars:master:3020190917180335:f1d02342 to ['x86_64'] based on the buildrequired module <ModuleBuild platform, id=1, stream=f30, version=6, scratch=False, state 'ready', batch 0, state_reason None>. info: Finding any buildrequired modules that collide with the RPMs in the base modules error: list_of_args and list_of_kwargs must be list or None. Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/module_build_service/scheduler/handlers/modules.py", line 193, in init handle_collisions_with_base_module_rpms(mmd, arches) File "/usr/lib/python3.7/site-packages/module_build_service/scheduler/default_modules.py", line 244, in handle_collisions_with_base_module_rpms bm_rpms = _get_rpms_from_tags(koji_session, bm_tags, arches) File "/usr/lib/python3.7/site-packages/module_build_service/scheduler/default_modules.py", line 292, in _get_rpms_from_tags koji_session, koji_session.listTaggedRPMS, tags, kwargs, File "/usr/lib/python3.7/site-packages/module_build_service/utils/general.py", line 153, in inner return function(*args, **kwargs) File "/usr/lib/python3.7/site-packages/module_build_service/builder/KojiModuleBuilder.py", line 154, in koji_retrying_multicall_map return koji_multicall_map(*args, **kwargs) File "/usr/lib/python3.7/site-packages/module_build_service/builder/KojiModuleBuilder.py", line 83, in koji_multicall_map raise ProgrammingError("list_of_args and list_of_kwargs must be list or None.") module_build_service.errors.ProgrammingError: list_of_args and list_of_kwargs must be list or None. info: State transition: 'init' -> 'failed', <ModuleBuild hedgewars, id=2, stream=master, version=3020190917180335, scratch=False, state 'failed', batch 0, state_reason 'An unknown error occurred while validating the modulemd'> info: Scheduling shutdown. info: Calling failed: MBSModule, 2 info: Scheduling shutdown. Traceback (most recent call last): File "/usr/bin/mbs-manager", line 11, in <module> load_entry_point('module-build-service==2.28.0', 'console_scripts', 'mbs-manager')() File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 286, in manager_wrapper manager.run() File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 417, in run result = self.handle(argv[0], argv[1:]) File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 386, in handle res = handle(*args, **config) File "/usr/lib/python3.7/site-packages/flask_script/commands.py", line 216, in __call__ return self.run(*args, **kwargs) File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 214, in build_module_locally raise RuntimeError("Module build failed") RuntimeError: Module build failed
Refer to comment https://bugzilla.redhat.com/show_bug.cgi?id=1752075#c4 for details.
Metadata Update from @cqi: - Issue assigned to cqi
Commit 0899e470 fixes this issue
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/mbs/issues/1420
Please continue any further discussion there.