A Backup that exists but cannot be read back is retried through the
controller's backoff, which left the BackupJob Running with nothing on
it saying why. Set Ready=False with reason BackupNotReadBack before
handing the error back.
When the check for an existing Backup itself fails, the Backup may well
exist, so a size probe would only be discarded, and a read that keeps
failing reran it, up to the probe timeout on the single BackupJob
worker, on every retry. Skip the probe in that case and create the
Backup without a size.
Drive both behaviours through the MariaDB and CNPG reconciles in tests.
Assisted-by: LLM
Signed-off-by: Andrey Kolkov <androndo@gmail.com>
Andrey Kolkov
080df1b2f2