CLDSRV-734: Revert back from go to python supervisord#5922
CLDSRV-734: Revert back from go to python supervisord#5922bert-e merged 1 commit intodevelopment/9.0from
Conversation
Hello bourgoismickael,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## development/9.0 #5922 +/- ##
================================================
Coverage 83.31% 83.31%
================================================
Files 189 189
Lines 12147 12147
================================================
Hits 10120 10120
Misses 2027 2027
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 |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
Will not merge for now, we will try to fix the divergence in supervisord.conf and try to use that same version into all our containers to have the same behavior everywhere. |
tcarmet
left a comment
There was a problem hiding this comment.
LGTM but for full fluent-bit access does it need the scality group to exists? If so, can you double check if usermode --login ${USER} is also creating a scality group (not only the user), if not let's modify the user creation to ensure we have one.
This will fix fluent-bit access to s3 log files The go version is not a perfect replacement it has multiple changes that would require to update supervisor conf. Breaking changes includes: - log files name changes - process number starts count at 1 instead of 0 - include full process_name with number in logfile - s3_1-1.log instead of s3-0.log - no supervisorctl, replaced by superivsord ctl with less option - no interactive supervisor ctl, if used without command it rewrite the superivsord.sock and then we lose access to supervisord ctl - replaced priority with depends_on - replaced %(ENV_X)s with envFiles Overrall we’d like to avoid breaking changes until we resolve correct usage of the go version and apply it in every component at once.
c0c5dc3 to
d6380a6
Compare
|
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: 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 |
|
/approve |
|
Merging as we don't have time to tacke the breaking changes for 9.5.1 |
Build failedThe build for commit did not succeed in branch bugfix/CLDSRV-734-supervisord-python The following options are set: approve, create_integration_branches |
Build failedThe build for commit did not succeed in branch w/9.1/bugfix/CLDSRV-734-supervisord-python The following options are set: approve, create_integration_branches |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-734. Goodbye bourgoismickael. The following options are set: approve, create_integration_branches |
This will fix fluent-bit access to s3 log files
The go version is not a perfect replacement it has multiple changes that would require to update supervisor conf.
Breaking changes includes:
Overrall we’d like to avoid breaking changes until we resolve correct usage of the go version and apply it in every component at once.