Skip to content

CLDSRV-1050: Keep the federation image home dir traversable by any uid - #6340

Open
dvasilas wants to merge 2 commits into
development/9.5from
bugfix/CLDSRV-1050-keep-federation-home-traversable
Open

dvasilas wants to merge 2 commits into
development/9.5from
bugfix/CLDSRV-1050-keep-federation-home-traversable

Conversation

@dvasilas

Copy link
Copy Markdown
Contributor

Since the image moved to Debian trixie (9.5.0-preview.6), /home/scality in the federation image has mode 700. Federation runs the container as the host scality user, so on any host where that user is not uid 1000, cloudserver fails at start-up with Cannot find module '/home/scality/s3/index.js'.

This PR gives the home dir back mode 755, and adds a CI step that runs the federation image as another uid.

Federation runs the container as the host user; the trixie base made /home/scality 700, so cloudserver could not reach index.js.
@bert-e

bert-e commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Hello dvasilas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request.
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Incorrect fix version

The Fix Version/s in issue CLDSRV-1050 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 9.5.1

  • 9.6.0

Please check the Fix Version/s of CLDSRV-1050, or the target
branch of this pull request.

@codecov

codecov Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.20%. Comparing base (76eed95) to head (198dbbc).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 1 file with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.5    #6340      +/-   ##
===================================================
- Coverage            90.23%   90.20%   -0.03%     
===================================================
  Files                  206      206              
  Lines                38673    38673              
===================================================
- Hits                 34897    34886      -11     
- Misses                3776     3787      +11     
Flag Coverage Δ
checksums-disabled-tests 46.21% <ø> (ø)
file-ft-tests 76.00% <ø> (ø)
file-ft-tests-null-compat 76.50% <ø> (ø)
kmip-ft-tests 37.72% <ø> (ø)
mongo-v0-ft-tests 77.07% <ø> (-0.03%) ⬇️
mongo-v1-ft-tests 77.10% <ø> (-0.01%) ⬇️
multiple-backend 44.56% <ø> (ø)
s3c-ft-tests-v0 71.71% <ø> (ø)
s3c-ft-tests-v0-null-compat 71.77% <ø> (-0.01%) ⬇️
s3c-ft-tests-v1 71.68% <ø> (ø)
sur-tests 45.15% <ø> (-0.03%) ⬇️
sur-tests-inflights 48.55% <ø> (-0.03%) ⬇️
unit 79.76% <ø> (ø)
utapi-v2-tests 45.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bert-e

bert-e commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@dvasilas

Copy link
Copy Markdown
Contributor Author

/create_integration_branches

@bert-e

bert-e commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1
  • development/9.2
  • development/9.3
  • development/9.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

@bert-e

bert-e commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants