nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can not store Attechments to S3

SvenF

Our Jira DC (9.12.x) is running on OpenShift.

We use the filestore-config.xml to setup our own S3 Bucket.

The feature flag was enabled correctly as per these instructions.

We have start the pod and in the jira-log we can read this:

"logger":"com.atlassian.jira.filestore.FileStoreSwitcher",
"message":"Due to the feature com.atlassian.jira.attachments.storage.configurable being disabled, the attachments storage is not configurable. Defaulting to attachments stored in the Jira home"

But for avatars ist works and they are stored in our S3 Bucket

What we are missing? Or is it not support on Jira?

if i call GET on the "DarkFeature" <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable

It returns "{"enabled": true}" so why the FileStoreSwitcher says it it disabled?

Accepted answers

SvenF

We found the "problem" ... it was the way how we enable the "DarkFeature"

On that page How to manage dark features in Jira | Jira | Atlassian Documentation the sentence

In order to enable a feature flag, type <feature_flag_name>.enabled in the Enable dark feature text area and click the Add button.

does not work with that DarkFeature.

We only have to add "com.atlassian.jira.attachments.storage.configurable" without the ".enabled" at the end and now it works as expected.

We can upload Attachment and they will be saved at the S3 Bucket.

Unfortunately, the corresponding rest call now shows "false". <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable BUT it works.

All comments

Yevhen_5guu4k

@SvenF you need to enable this dark feature. See the warning block in https://confluence.atlassian.com/adminjiraserver0912/storing-attachments-in-amazon-s3-1346048178.html

SvenF

Thank you, but as I wrote above "The feature flag was enabled correctly as per these instructions." It is enabled.

And I have also restart the pod, but the flag seems to be ignored.

Yevhen_5guu4k

Sorry, I missed it completely that you did enabled this feature. It should be supported for this Jira version as far I know, but I am not a Jira SME.

SvenF

no problem.

On that page Configuring file attachments | Administering Jira applications Data Center 9.12 | Atlassian Documentation

there is one sentense:

"This feature isn't supported for on-premise deployments or for any customers not running Jira in AWS."

So did we need a real AWS Bucket?

I wish I could take a look in the FileStoreSwitcher class ...

SvenF

We found the "problem" ... it was the way how we enable the "DarkFeature"

On that page How to manage dark features in Jira | Jira | Atlassian Documentation the sentence

In order to enable a feature flag, type <feature_flag_name>.enabled in the Enable dark feature text area and click the Add button.

does not work with that DarkFeature.

We only have to add "com.atlassian.jira.attachments.storage.configurable" without the ".enabled" at the end and now it works as expected.

We can upload Attachment and they will be saved at the S3 Bucket.

Unfortunately, the corresponding rest call now shows "false". <baseURL>/rest/internal/1.0/darkFeatures/com.atlassian.jira.attachments.storage.configurable BUT it works.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

attachment

data-center

bucket