IQSS / IQSS/dataverse

Azure File Compatibility issue

Open
#12,356 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Hi Team,

Gud Mrg

Currently we are working  on deploying Dataverse application on azure into Azure Container Apps.

What steps does it take to reproduce the issue?
As of now we are using azure files for storing the files when user upload in datasets those files need to come and store in azure storage account azure files what ever we have mounted as volumes in dataverse container app.

  • When does this issue occur?

  • Which page(s) does it occurs on?

Image Image
  • What happens?
    We are able to upload the file in datasets and publishing successfully and we are able to see the and download the files in dataverse aca in dv/xz>>>path but the issue is the file is not getting stored in azure files what ever we have given in azure mount, next if we restart dataverse container app we are getting 400 error for the same files as it is unable tomsee the file path ass it;s stored temporally .

  • To whom does it occur (all users, curators, superusers)?

super user

  • What did you expect to happen?

-the files we have uploaded need to save in azure files as we are getting compatability issue files are getting stored in dataverse container app.
-will azure fiels will support dataverser aca enviornement

Which version of Dataverse are you using?

dataverse:6.10.1-noble

Any related open or closed issues to this bug report?

-this is the first issue we are creating
Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names Dataverse 6.10.1-noble on Azure Container Apps with Azure Files mounted as volumes, but no source files or tests. Start by reproducing upload, publish, restart, and download behavior in that deployment and inspect the storage and mount configuration path. Done means uploaded files persist in Azure Files and remain accessible after restart without 400 errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.