Skip to content

docs(troubleshooting): explain the "no backup section" error - #1166

Open
fjvbn2003 wants to merge 1 commit into
cloudnative-pg:mainfrom
fjvbn2003:docs-troubleshooting-no-backup-section
Open

fjvbn2003 wants to merge 1 commit into
cloudnative-pg:mainfrom
fjvbn2003:docs-troubleshooting-no-backup-section

Conversation

@fjvbn2003

Copy link
Copy Markdown

Closes #1165

Adds the error cannot proceed with the backup as the cluster has no backup section to "Backup job fails immediately" in troubleshooting.md.

The cause is a Backup or ScheduledBackup without method: plugin: method
defaults to barmanObjectStore, and the operator then requires a
.spec.backup section that a Cluster using the plugin usually does not have
(internal/controller/backup_controller.go in the operator). The entry shows
the fix for the resources and for kubectl cnpg backup (-m plugin --plugin-name barman-cloud.cloudnative-pg.io), as discussed in #353.

How I checked: on CNPG 1.30, kubectl explain backup.spec.method and the
Backup and ScheduledBackup CRDs both show the barmanObjectStore default.
I hit the error with a ScheduledBackup after migrating to the plugin, and
adding method: plugin fixed it.

This change was drafted with AI assistance and reviewed by me.

🤖 Generated with Claude Code

A Backup or ScheduledBackup without method: plugin falls back to the
default barmanObjectStore method. The operator then requires a
.spec.backup section in the Cluster, which a Cluster using the plugin
usually does not have, and the backup fails with "cannot proceed with
the backup as the cluster has no backup section".

Add this to the list of immediate backup failures, with the fix for
Backup and ScheduledBackup resources and for kubectl cnpg backup, as
discussed in cloudnative-pg#353.

Assisted-by: Claude Opus 5.5
Signed-off-by: YoungjuKim <fjvbn2003@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: troubleshooting does not cover "cannot proceed with the backup as the cluster has no backup section"

1 participant