Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.1.0
-
Untriaged
-
1
-
Unknown
-
Tools 2022-Jan, Tools 2022-Feb
Description
7.1.0-2097
Test:
-test tests/integration/neo/test_neo_couchstore_milestone4.yml -scope tests/integration/neo/scope_couchstore.yml
Scale 3
Iteration 1
Tried to add a s3 backup repo to the longevity cluster - failed with following error:
2022-01-20T11:50:20.342-08:00 (Cmd) cbbackupmgr version 7.1.0-2097 Hostname: cnt7-qe1 OS: linux Version: 3.10.0-693.5.2.el7.x86_64 Arch: amd64 vCPU: 8 Memory: 25107591168 (23.38GiB)
|
2022-01-20T11:50:20.342-08:00 (Cmd) config --archive s3://backup-service-testing/longevity-testing/centos1 --repo b2025d58-7535-4058-baa9-4e2a91af6f1a --cbbs --readme-author Backup Service, cluster: e283f49510e59e9f2f15f94159c565fa --obj-region eu-west-2 --obj-staging-dir /data/s3/my_repo_s3-b2025d58-7535-4058-baa9-4e2a91af6f1a
|
2022-01-20T11:50:20.342-08:00 (Cmd) mounted archive with id: d96c3dae-9d33-4d02-8031-4b83714c96f1
|
2022-01-20T11:50:20.344-08:00 (Cmd) Backup repository `b2025d58-7535-4058-baa9-4e2a91af6f1a` created successfully in archive `s3://backup-service-testing/longevity-testing/centos1`
|
2022-01-20T11:50:31.507-08:00 (Cmd) Post sub-command object store task failed: failed to sync staging directory: failed to upload archive metadata: failed to upload archive logs: failed to stop pool: failed to upload file: failed to complete upload: failed to stop worker pool: failed to upload part: RequestError: send request failed
|
caused by: Put "https://backup-service-testing.s3.eu-west-2.amazonaws.com/longevity-testing/centos1/logs/backup-1.log?partNumber=31&uploadId=saBTS0eXU52amOOtoHSraMolQRoumv_nwe.NrJllnGeLQqoBxSjmgpyAccz9unmleMMcc_BrFCJob1gomE3jwugEzI0uFgxFdfFDu.HpyBcA5gXScJpOTx5W8DBS_wzL": net/http: HTTP/1.x transport connection broken: http: ContentLength=5242880 with Body length 2102755
|
Attaching screenshot and backup logs
Attachments
Issue Links
- relates to
-
MB-54213 [CBM] Panic on restore if we can't open or create the stats folder
- Closed