Description of problem:

Note: 10 year old design flaw

If repo creation / syncing / CV publishing is automated via the API, it's possible for users to try publishing the repo in a CV while metadata generation is still running. This isn't so much of an issue from the UI,  but in automation, these steps can  happen very quickly.

How reproducible:

Probably easily, QE has workarounds for it.

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

Automate creating a repository and them publishing it in a CV.

Actual behavior:
An error is returned that says the repository is locked due to being part of a metadata generation task.

Expected behavior:
Metadata generation is part of the normal repository creation workflow.

Business Impact / Additional info:

Original redmine that introduced this: https://projects.theforeman.org/issues/9585

It looks like it was part of an effort to speed up Red Hat repository enabling. Nowadays, metadata generation for empty repositories should be really fast, so I don't see why it should slow down repository enablement.