No valid configuration files found #662
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#662
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Create backup
Steps to reproduce (if a bug)
Was working until upgrade to 1.7.10.
Error:
Location of yaml: /etc/borgmatic.d/config.yaml
Config contents:
Docker-compose:
Logs:
OS: Ubuntu 22.04
Docker container.
Dockerfile: https://github.com/modem7/docker-borgmatic/blob/master/base-fullbuild/Dockerfile
Nice, thanks for filing this!
For context, I recently worked on this PR - https://github.com/borgmatic-collective/borgmatic/pull/57, which allows users to tag/label a repo, hence changing the data structure of repositories throughout the codebase ( from a
str
to adict
with keyspath
andlabel
).Now I knew I could miss something out and that's exactly what happened 😅.
In this case particularly -
validate.py::apply_logical_validation()
fails because it expects the repositories in the parsed configuration to be a list of strings, which we changed to a list of dicts.This is what the quick
print
statement results in:Hence, the error that you are facing. @witten I'll patch a fix for this, looking for other
repository
references in thevalidate.py
file too. Do you know any other place in the config where a reference to the repositories key is made?This means I can add label support to the
check_repositories
array too. Again, really helpful ticket, I was looking for community feedback and got it in a single day!Oh thank god - I thought I screwed something up (usually the case), especially as two other VMs (albeit with one repo attached rather than multiple) were working!
Thanks for the quick response and I'm glad it was a productive ticket!!
Yes, thanks for jumping in @diivi. And @modem7, I appreciate the detailed ticket. You can likely comment out
check_repositories
in order to get borgmatic working again, at least in the interim. We'll keep you updated.PR: https://github.com/borgmatic-collective/borgmatic/pull/63
Okay, @diivi has fixed this in master and it will be part of the next release. I was hoping not to do an immediate fix release, but we'll see if any other bugs crop up. Thanks again for reporting this.
Thank you guys for this amazingly quick turnaround!