ovh / ovh/docs

bug: Rclone config missing storage_class

Open
#9,404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
273
Forks
391
Avg merge
1m
Merged PRs (30d)
1

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

The documention and the file generated by the manager are missing the storage_class parameter, default to storage_class = STANDARD (uppercase).
Without it, you get such errors :

rclone sync azure:backup ovh:bucket/backup
2026/05/26 00:00:16 ERROR : backup.zip: Failed to copy: operation error S3: PutObject, https response error StatusCode: 400, RequestID: txa5cde5a9a0c546119ad05-006a14e290, HostID: txa5cde5a9a0c546119ad05-006a14e290, api error InvalidStorageClass: The storage class you specified is not valid

Expected Behavior

The manager should generate a functional file.
The documentation should mention the storage_class parameter.

Steps To Reproduce

No response

Describe alternatives you've considered

No response

Which operating systems have you used?

None

Which web browser have you used?

None

Anything else?

No response

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

Start by locating the manager generator and documentation section that produce the rclone configuration; search for existing storage parameters and the missing storage_class entry. Reproduce the reported output or inspect the generated file, then confirm both the file and documentation include storage_class=STANDARD and that the generated configuration is functional.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.