Only the job that attaches the barman-cloud plugin waited for the
instance rollout it causes. A second job of the same application that
started meanwhile found the plugin already there, had no rollout of its
own to wait for and created its cnpg.io/Backup at once, against
instances CNPG was still recreating, and such a Backup fails for good.
The queue does not hold it either, since the attaching job has no
Backup yet.
The attach record on the Cluster says when the plugin was attached, so
a job without a rollout of its own now waits for instances newer than
it while the attach is recent enough for that rollout to be running.
An older attach has had its rollout judged by the job that made it.
The record belongs to that job, so one this job cannot read, or one
further ahead than controller clocks drift, is skipped rather than
failing it; the latter would otherwise hold every later job of the
application for as long as it lies ahead.
Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>