Repository navigation
Conversation
Federation runs the container as the host user; the trixie base made /home/scality 700, so cloudserver could not reach index.js.
Hello dvasilas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
@@ 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
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
Since the image moved to Debian trixie (9.5.0-preview.6),
/home/scalityin the federation image has mode 700. Federation runs the container as the hostscalityuser, so on any host where that user is not uid 1000, cloudserver fails at start-up withCannot 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.