Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.1.0
-
Untriaged
-
1
-
No
Description
7.1.0-1742
On our longevity cluster, I manually configured two cloud repose - my_s3_repo with /data/s3 as the staging directory and my_gcp_repo with /data/gcp as the staging directory. Verified that /data/s3 and /data/gcp are owned by couchbase and all the subdirectories and files created by CBM are owned by couchbase as well:
Now, I executed the following collect-logs command with ~/ as the output directory:
/opt/couchbase/bin/cbbackupmgr collect-logs -a s3://backup-service-testing/longevity-testing -o ~/ --obj-staging-dir /data/s3/my_s3_repo-bcfa488c-69a8-4576-bd1c-87d9847ec229/ --obj-access-key-id xxx --obj-secret-access-key xxx --obj-region eu-west-2
Logs got collected successfully (attached). But when I check the directories again now, we can see that .info and backup-0.log files are now owned by root and not couchbase:
We can also see that the following error is thrown on the repo now:
Could not get repository information: Could not get repository info. exit status 1 - {"error":"existing staging directory is for another cloud provider, retry with another one or recreate the existing one"}
Attaching screenshot for the same