BB-743 missing scality group on docker image

[tcarmet]

A scality user and group is required for the federation image. Now creating both and adding the scality user to the node group

Before:

scality@c3de243e2c65:~/backbeat$ id scality          
uid=1000(scality) gid=1000(node) groups=1000(node)   

After:

scality@e506d63687e3:~/backbeat$ id                                            
uid=1001(scality) gid=1001(scality) groups=1001(scality),1000(node)            

[bert-e]

Hello tcarmet,

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	⭐
/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 TBA
/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]

Incorrect fix version

The Fix Version/s in issue BB-743 contains:

• None

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

• 9.0.23

• 9.1.6

• 9.2.1

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.39%. Comparing base (0994bb0) to head (162b308).
⚠️ Report is 2 commits behind head on development/9.0.

Additional details and impacted files

see 5 files with indirect coverage changes

Components	Coverage Δ
Bucket Notification	80.20% <ø> (ø)
Core Library	81.14% <ø> (+0.18%)	⬆️
Ingestion	70.81% <ø> (+0.52%)	⬆️
Lifecycle	78.67% <ø> (ø)
Oplog Populator	85.06% <ø> (ø)
Replication	58.48% <ø> (ø)
Bucket Scanner	85.76% <ø> (ø)

@@                 Coverage Diff                 @@
##           development/9.0    #2714      +/-   ##
===================================================
+ Coverage            74.27%   74.39%   +0.11%     
===================================================
  Files                  202      202              
  Lines                13472    13472              
===================================================
+ Hits                 10006    10022      +16     
+ Misses                3456     3440      -16     
  Partials                10       10              

Flag	Coverage Δ
api:retry	9.45% <ø> (ø)
api:routes	9.26% <ø> (ø)
bucket-scanner	85.76% <ø> (ø)
ft_test:queuepopulator	10.19% <ø> (-0.56%)	⬇️
ingestion	12.56% <ø> (+0.05%)	⬆️
lib	7.46% <ø> (-0.01%)	⬇️
lifecycle	18.65% <ø> (ø)
notification	1.04% <ø> (ø)
replication	18.61% <ø> (+0.10%)	⬆️
unit	50.01% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bert-e]

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.

[tcarmet]

/create_integration_branches

[bert-e]

Integration data created

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

• this pull request will merge bugfix/BB-743-scality-group-missing-federation-image into
  development/9.0
• w/9.1/bugfix/BB-743-scality-group-missing-federation-image will be merged into development/9.1
• w/9.2/bugfix/BB-743-scality-group-missing-federation-image will be merged into development/9.2

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.6

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]

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

[tcarmet]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/9.0

• ✔️ development/9.1

• ✔️ development/9.2

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.6

Please check the status of the associated issue BB-743.

Goodbye tcarmet.

The following options are set: approve, create_integration_branches