Fix compatibility issue of s3 backup

[wangzw]

Back port #6354 #6355 #6382 to 6.3 release

Code-Reviewer Section

The general guidelines can be found here.

Please check each of the following things and check all boxes before accepting a PR.

• [ ] The PR has a description, explaining both the problem and the solution.
• [ ] The description mentions which forms of testing were done and the testing seems reasonable.
• [ ] Every function/class/actor that was touched is reasonably well documented.

For Release-Branches

If this PR is made against a release-branch, please also check the following:

• [ ] This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or master if this is the youngest branch)
• [ ] There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: 289396237294706c7e0ff5d8a373ece0b4fc4199
• Result: FAILED
• Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for macOS BigSur 11.5.2

• CodeBuild project: foundationdb-pr-macos
• Commit ID: 289396237294706c7e0ff5d8a373ece0b4fc4199
• Result: FAILED
• Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /usr/local/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 289396237294706c7e0ff5d8a373ece0b4fc4199
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[jzhou77]

Can you make a PR against the main branch too?

[wangzw]

Can you make a PR against the main branch too?

Since it is not easy to cherry pick to main branch, I file a new pull request for main branch. #6354

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: fa3ef974262671a83c052ba261870ebb1b89a2e5
• Result: FAILED
• Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for macOS BigSur 11.5.2

• CodeBuild project: foundationdb-pr-macos
• Commit ID: fa3ef974262671a83c052ba261870ebb1b89a2e5
• Result: FAILED
• Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /usr/local/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: fa3ef974262671a83c052ba261870ebb1b89a2e5
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: 49cc9e2f9e7ed5abaa4a047d6a38b8685fb70cfe
• Result: FAILED
• Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for macOS BigSur 11.5.2

• CodeBuild project: foundationdb-pr-macos
• Commit ID: 49cc9e2f9e7ed5abaa4a047d6a38b8685fb70cfe
• Result: FAILED
• Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /usr/local/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 49cc9e2f9e7ed5abaa4a047d6a38b8685fb70cfe
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: 51e99b52ab8d62a7b26f7e80a58db6806dd548a0
• Result: FAILED
• Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 51e99b52ab8d62a7b26f7e80a58db6806dd548a0
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 217a8f8ba9c1a69f81a97d83bdea4db29ceb3e60
• Result: :x: FAILED
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: 217a8f8ba9c1a69f81a97d83bdea4db29ceb3e60
• Result: FAILED
• Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 481e7d32156d46d7a443fa20ba8fa4abffd56fcb
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[foundationdb-ci]

AWS CodeBuild CI Report for Linux CentOS 7

• CodeBuild project: foundationdb-pr
• Commit ID: 481e7d32156d46d7a443fa20ba8fa4abffd56fcb
• Result: SUCCEEDED
• Error: N/A
• Build Logs (available for 30 days)

[bnamasivayam]

Let the corresponding changes on main branch get some soak time and then we could look at merging it on 6.3, 7.0 and 7.1.

[foundationdb-ci]

Result of foundationdb-pr-macos on macOS BigSur 11.5.2

• Commit ID: 160fbbf4d08016a8099b7b369c43646154262cf1
• Duration 0:06:10
• Result: :x: FAILED
• Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /usr/local/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
• Build Logs (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 160fbbf4d08016a8099b7b369c43646154262cf1
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr on Linux CentOS 7

• Commit ID: 160fbbf4d08016a8099b7b369c43646154262cf1
• Duration 0:30:15
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Logs (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

• Commit ID: 160fbbf4d08016a8099b7b369c43646154262cf1
• Duration 4:16:54
• Result: :x: FAILED
• Error: Build has timed out.
• Build Logs (available for 30 days)

[wangzw]

Let the corresponding changes on main branch get some soak time and then we could look at merging it on 6.3, 7.0 and 7.1.

Hi @bnamasivayam

Is it ok to back port to 6.3 now? We need a 6.3 release to updating our production environment.

[foundationdb-ci]

Result of foundationdb-pr-macos on macOS BigSur 11.5.2

• Commit ID: 328a115e04f11cad592474a4c381462a9ce523d4
• Duration 0:17:10
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)

[fdb-windows-ci]

Doxense CI Report for Windows 10

• Commit ID: 328a115e04f11cad592474a4c381462a9ce523d4
• Result: :heavy_check_mark: SUCCEEDED
• Build Logs (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr on Linux CentOS 7

• Commit ID: 328a115e04f11cad592474a4c381462a9ce523d4
• Duration 0:47:05
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

• Commit ID: 328a115e04f11cad592474a4c381462a9ce523d4
• Duration 1:01:34
• Result: :x: FAILED
• Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos-m1 on macOS BigSur 11.5.2

• Commit ID: bb568a475841fc024ca4bf341f1dfa889ad9dbe2
• Duration 0:05:47
• Result: :x: FAILED
• Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /opt/homebrew/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-clang on Linux CentOS 7

• Commit ID: bb568a475841fc024ca4bf341f1dfa889ad9dbe2
• Duration 0:06:08
• Result: :x: FAILED
• Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos on macOS Monterey 12.x

• Commit ID: bb568a475841fc024ca4bf341f1dfa889ad9dbe2
• Duration 0:19:38
• Result: :white_check_mark: SUCCEEDED
• Error: N/A
• Build Logs (available for 30 days)
• Build Artifact (available for 30 days)