fix(fs): handle object storage server not implementing Object lock (#7157)
This commit is contained in:
committed by
GitHub
parent
cabd04470d
commit
2bfdb60dda
@@ -456,7 +456,7 @@ export default class S3Handler extends RemoteHandlerAbstract {
|
||||
this.#s3.middlewareStack.use(getApplyMd5BodyChecksumPlugin(this.#s3.config))
|
||||
}
|
||||
} catch (error) {
|
||||
if (error.Code !== 'ObjectLockConfigurationNotFoundError') {
|
||||
if (error.Code !== 'ObjectLockConfigurationNotFoundError' && error.$metadata.httpStatusCode !== 501) {
|
||||
throw error
|
||||
}
|
||||
}
|
||||
|
||||
@@ -15,6 +15,7 @@
|
||||
- [Netbox] Fix "400 Bad Request" error (PR [#7153](https://github.com/vatesfr/xen-orchestra/pull/7153))
|
||||
- [Backup/Restore] Fix timeout after 5 minutes [#7052](https://github.com/vatesfr/xen-orchestra/issues/7052)
|
||||
- [Dashboard/Health] Empty VDIs are no longer considered orphans (PR [#7102](https://github.com/vatesfr/xen-orchestra/pull/7102))
|
||||
- [S3] Handle S3 without *Object Lock* implementation (PR [#7157](https://github.com/vatesfr/xen-orchestra/pull/7157))
|
||||
|
||||
### Packages to release
|
||||
|
||||
@@ -32,7 +33,9 @@
|
||||
|
||||
<!--packages-start-->
|
||||
|
||||
- @xen-orchestra/fs patch
|
||||
- @xen-orchestra/proxy patch
|
||||
- xo-server-netbox patch
|
||||
- xo-web patch
|
||||
|
||||
<!--packages-end-->
|
||||
|
||||
Reference in New Issue
Block a user