You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the backup-manager.py command while a backup is running started to list the backup sets and then died with this error..
Traceback (most recent call last):
File "/usr/local/sbin/backup-manager.py", line 420, in
main()
File "/usr/local/sbin/backup-manager.py", line 293, in main
hostnames = list_backups(bucket)
File "/usr/local/sbin/backup-manager.py", line 91, in list_backups
backupnum = int(keyparts.pop())
ValueError: invalid literal for int() with base 10: 'COMPLETE'
I browsed my S3 files and noticed one odd file. In one of the backup folders, I have a ..tar.COMPLETE.gpg file. That doesn't seem to match. I'm not exactly sure what the keyparts.pop() is doing in the script, but I think these things are related. I think I'll just delete this extra file and see what happens. Not sure if you thought any code changes were warranted for this condition.
The text was updated successfully, but these errors were encountered:
Running the backup-manager.py command while a backup is running started to list the backup sets and then died with this error..
Traceback (most recent call last):
File "/usr/local/sbin/backup-manager.py", line 420, in
main()
File "/usr/local/sbin/backup-manager.py", line 293, in main
hostnames = list_backups(bucket)
File "/usr/local/sbin/backup-manager.py", line 91, in list_backups
backupnum = int(keyparts.pop())
ValueError: invalid literal for int() with base 10: 'COMPLETE'
I browsed my S3 files and noticed one odd file. In one of the backup folders, I have a ..tar.COMPLETE.gpg file. That doesn't seem to match. I'm not exactly sure what the keyparts.pop() is doing in the script, but I think these things are related. I think I'll just delete this extra file and see what happens. Not sure if you thought any code changes were warranted for this condition.
The text was updated successfully, but these errors were encountered: