Revert "Push deb packages to Pulp with one repository version per repo"

🤖 beep boop — clanker comment.

What does this MR do?

Reverts !7286 (merged) (merge commit 5df162b4), restoring the previous deb push to Pulp and dropping RUNNER_MAGE_CONCURRENCY: "4" from .release_pulp.

Why was this MR needed?

unstable pulp: [ubuntu] and [debian] have failed on every main pipeline since the merge (2832514319, 2832545732) with

Error: ["Destination upload repository was not provided."]

The new pusher uploads packages and creates the release link units without naming a repository, so that each repository gets one version and one publish. pulpcore's access policy for content creation (has_required_repo_perms_on_upload) only allows that for superusers; any other user must pass repository, which brings back one version and one publish per call. Two of the four content endpoints involved (release_components, release_architectures) are admin-only by default on top of that. The sandbox the change was verified against used the admin account, so none of this showed up before the merge.

There is no forward fix inside the runner repository. The options (autopublish off on the deb repos with one explicit publish at the end of the job, a staging repository without autopublish, or a customised access policy for the CI user) all need a change on the Pulp side and are tracked in gitlab-com/gl-infra/production-engineering#29705.

Also reverts the concurrency bump: the rpm jobs in the same two pipelines hit HTTP 500s from pulp.gitlab.com, which they had not done before. Not shown to be related, but not worth keeping while the rest is out.

What are the relevant issue numbers?

gitlab-com/gl-infra/production-engineering#29705

Merge request reports

Loading
Loading