Skip to content

[Bug]: Backups are still tried for hibernated clusters #8508

@simonapencea

Description

@simonapencea

Is there an existing issue already for this bug?

  • I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

  • I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

  • I have read the troubleshooting guide and I think this is a new bug.

Contact Details

simona@xata.io

Version

1.26 (latest patch)

What version of Kubernetes are you using?

1.33

What is your Kubernetes environment?

Other

How did you install the operator?

YAML manifest

What happened?

We are creating Clusters and for each cluster we also create a ScheduledBackup to provide continuous backups.
Sometimes we want to hibernate those clusters.

What happened:

  • when we use the provided annotation here:
    https://cloudnative-pg.io/documentation/1.26/declarative_hibernation/#hibernation
    to hibernate the cluster, the ScheduledBackup remains active.
    This means it will still trigger a full backup according to the schedule and if at that time the cluster is hibernated, the full backup fails. It fails because it cannot find the pod, which is normal for a hibernated cluster. But it is still a failing backup that needs to be investigated - it will trigger an alarm, page someone, we see it in the logs etc.

What we expected to happen:

Cluster resource


Relevant log output


Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

triagePending triage

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions