(apologies if you get this twice; I wasn't able to log in yesterday so I had sent an email (which may not have gotten through))
After upgrading from 1.33.2 to 1.35.3 we've been seeing builds fail due to malformed waitrepo tasks (that's what the command-line interface calls them). Here's an example: waitrepo (osg-23-main-el9-build, )
waitrepo
After waiting for several minutes, eventually the task fails with ParameterError: handler() takes from 2 to 4 positional arguments but 5 were given. So far I've worked around it by disabling kojira and running regen-repo tasks by hand.
ParameterError: handler() takes from 2 to 4 positional arguments but 5 were given
Do you have any suggestions? This is bothersome enough that I'm considering downgrading (not a fun process due to having to undo the DB schema change…)
It sounds like you still have builders that are still running an older version of koji.
Koji generally assumes that all core systems (hub, web, builders, util) are running the same version. We try to maintain compatibility in the api for older clients, but the builders are considered internal to the system.
I suppose it could be the case they this builder was updated, but the service wasn't restarted.
Clearly at least some of your other builders are updated since this subtask was created by one with the new parameters.
Metadata Update from @mikem: - Custom field Size adjusted to None
Hi Mike, thanks for your response. That does indeed explain it -- one of our builders was running an old container image because we were using it for building for el7 and mock 5.0+ broke our el7 builds by attempting to install 'python3-dnf', which was not available. We still have the need of the occasional el7 build (for containers) so I will attempt to make a new image with an upgraded koji, while holding back mock.
Metadata Update from @mikem: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/4410
Please continue any further discussion there.