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

KeyError: 'backup_name' on WAL-E restore from S3 #1070

Open
harvetech opened this issue Jan 9, 2025 · 1 comment
Open

KeyError: 'backup_name' on WAL-E restore from S3 #1070

harvetech opened this issue Jan 9, 2025 · 1 comment

Comments

@harvetech
Copy link

return match.get('name', match['backup_name'])

It seems like this above-mentioned line is creating issues on restore. I am consistently getting this error on restoring WAL-E based backup.


> wal_e.main   INFO     MSG: starting WAL-E
>         DETAIL: The subcommand is "backup-list".
>         STRUCTURED: time=2025-01-09T07:16:42.273651-00 pid=165
> 2025-01-09 07:16:42,584 ERROR: Clone failed
> Traceback (most recent call last):
>   File "/scripts/clone_with_wale.py", line 184, in main
>     run_clone_from_s3(options)
>   File "/scripts/clone_with_wale.py", line 165, in run_clone_from_s3
>     backup_name, update_envdir = find_backup(options.recovery_target_time, env)
>   File "/scripts/clone_with_wale.py", line 152, in find_backup
>     backup = choose_backup(backup_list, recovery_target_time)
>   File "/scripts/clone_with_wale.py", line 78, in choose_backup
>     return match.get('name', match['backup_name'])
> KeyError: 'backup_name'

These are my ENV variable for the spilo Image

CLONE_WAL_BUCKET_SCOPE_PREFIX: ""
CLONE_WAL_S3_BUCKET: ${BUCKET_NAME}
CLONE_AWS_S3_FORCE_PATH_STYLE: "true"
CLONE_TARGET_TIMELINE: "latest"
CLONE_SCOPE: "r-db"
CLONE_USE_WALG_RESTORE: "false"

@thismatters
Copy link

I am also seeing this issue. The WAL-E backup-list command uses the key name; backup_name doesn't appear anywhere.

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

No branches or pull requests

2 participants