fix(@xen-orchestra/fs): handle object storage server not implementing Object lock
This commit is contained in:
@@ -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
|
||||
}
|
||||
}
|
||||
|
||||
@@ -12,6 +12,7 @@
|
||||
> Users must be able to say: “I had this issue, happy to know it's fixed”
|
||||
|
||||
- [Netbox] Fix VMs' `site` property being unnecessarily updated on some versions of Netbox (PR [#7145](https://github.com/vatesfr/xen-orchestra/pull/7145))
|
||||
- [S3] Handle S3 without Object Lock implementation (PR [#7157](https://github.com/vatesfr/xen-orchestra/pull/7157))
|
||||
|
||||
### Packages to release
|
||||
|
||||
@@ -29,6 +30,7 @@
|
||||
|
||||
<!--packages-start-->
|
||||
|
||||
- @xen-orchestra/fs patch
|
||||
- xo-server-netbox patch
|
||||
|
||||
<!--packages-end-->
|
||||
|
||||
Reference in New Issue
Block a user