You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prerequisite : Odoo is deployed with a Docker container and so running on Ubuntu image, fs_storage is installed, configuring a S3 storage like in development environment. Behavior is different between development and docker-deployed environment. When attaching an ir_attachment to S3, it either does not work or Odoo runs until timeout.
Install docker image on web server (we use Scaleway provider to create an instance and install docker + docker-compose), contact me if any help is needed
Install fs_storage module in Odoo and configure an S3 attachment storage for res.partner for example
Add an attachment to a res.partner
First try resolves to not adding the attachment at all (when refreshing with F5, attachment disappears). Second try, application runs with spinner indefinitely (until timeout)
Expected behavior
Attachment should be created in S3 mentioned directory.
Additional context
I use an Object storage (from Scaleway) (S3).
Connection test is successful
Tried with and without optimizes directory
Using a simple directory path "Archipell"
Tried every directory path
The text was updated successfully, but these errors were encountered:
Module
fs_storage
Describe the bug
Prerequisite : Odoo is deployed with a Docker container and so running on Ubuntu image, fs_storage is installed, configuring a S3 storage like in development environment. Behavior is different between development and docker-deployed environment. When attaching an ir_attachment to S3, it either does not work or Odoo runs until timeout.
To Reproduce
Affected versions: v16.0.
Python: 3.9.
Odoo docker image: v16.0 from 01/01/2024.
fsspec: 2024.2.0
Steps to reproduce the behavior:
Expected behavior
Attachment should be created in S3 mentioned directory.
Additional context
I use an Object storage (from Scaleway) (S3).
The text was updated successfully, but these errors were encountered: