Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: There is no problem with backups, but I still see "Last Failed Backup Time" alert. #4512

Open
4 tasks done
kfkawalec opened this issue May 11, 2024 · 0 comments
Open
4 tasks done
Assignees
Labels
triage Pending triage

Comments

@kfkawalec
Copy link

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

No response

Version

1.21.5

What version of Kubernetes are you using?

1.27

What is your Kubernetes environment?

Self-managed: RKE

How did you install the operator?

Helm

What happened?

"Last Failed Backup Time" is firing.
cnpg_collector_last_failed_backup_timestamp > 1 -> show "1715294339"

Cluster resource

No response

Relevant log output

Continuous Backup status
First Point of Recoverability:  2024-03-24T01:51:29Z
Working WAL archiving:          OK
WALs waiting to be archived:    0
Last Archived WAL:              000000150000016000000075   @   2024-05-11T07:42:43.778192Z
Last Failed WAL:                -

Code of Conduct

  • I agree to follow this project's Code of Conduct
@kfkawalec kfkawalec added the triage Pending triage label May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Pending triage
Projects
None yet
Development

No branches or pull requests

2 participants