-
Notifications
You must be signed in to change notification settings - Fork 107
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] Backup/recovery commands fail when default configuration for backup attached to cluster-config.yml #2930
Closed
8 of 18 tasks
Labels
Comments
cicharka
added a commit
to cicharka/epiphany
that referenced
this issue
Feb 9, 2022
Bug hitachienergy#2942 rsync command fails trying to copy artifacts * With new version of ansible we can use private_key option for synchronize module, therefore there's no need to use rsh Bug hitachienergy#2930 Backup/recovery commands fail when default configuration for backup attached to cluster-config.yml * extend run_for_individual_documents method so it can choose relevant schema for validated document
cicharka
added a commit
to cicharka/epiphany
that referenced
this issue
Feb 14, 2022
Bug hitachienergy#2942 rsync command fails trying to copy artifacts * With new version of ansible we can use private_key option for synchronize module, therefore there's no need to use rsh Bug hitachienergy#2930 Backup/recovery commands fail when default configuration for backup attached to cluster-config.yml * extend run_for_individual_documents method so it can choose relevant schema for validated document
cicharka
added a commit
to cicharka/epiphany
that referenced
this issue
Feb 23, 2022
Bug hitachienergy#2942 rsync command fails trying to copy artifacts * With new version of ansible we can use private_key option for synchronize module, therefore there's no need to use rsh Bug hitachienergy#2930 Backup/recovery commands fail when default configuration for backup attached to cluster-config.yml * extend run_for_individual_documents method so it can choose relevant schema for validated document
After conversations with @przemyslavic and @seriva there is agreement:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Documentation for backup/recovery states that it is possible to attach default backup/recovery configuration from
defaults/configuration/backup.yml
/defaults/configuration/recovery.yml
tocluster-config.yml
, but in both cases runningepicli backup
/epicli recovery
fails due to the error:It is important to note that backup and recovery commands work fine when there's a newly created backup.yml or recovery.yml file which contain only default backup/recovery configuration.
How to reproduce
Steps to reproduce the behavior for backup:
defaults/configuration/backup.yml
and attach it to existingcluster-config.yml
(can be a copy of that file as well -> important part here is to have your previous configuration statements and the backup section in one file)epicli backup ...
commandSteps to reproduce the behavior for recovery:
epicli recovery ...
commandExpected behavior
Attaching recovery/backup configuration to existing configuration file will not make
epicli backup/recovery
commands fail -> operations will succeedEnvironment
epicli version: [
epicli --version
]v2.0dev
Additional context
Verify if it is needed to test it in previous releases.
DoD checklist
The text was updated successfully, but these errors were encountered: