Cherry pick #85734 to 25.3: Fix incorrect distinguishment between *Cluster and Distributed for object storage#85839
Conversation
Fix incorrect distinguishment between `*Cluster` and `Distributed` for object storage
|
Dear @thevar1able, the PR is not updated for 1d0h59m6s. Please, either resolve the conflicts, or close it to finish the backport process of #85734 |
|
The release branch |
|
Hey @thevar1able - do you have a rough ETA for when this will get merged? We're experiencing this issue 😞 |
|
Dear @thevar1able, the PR is not updated for 1d0h16m45s. Please, either resolve the conflicts, or close it to finish the backport process of #85734 |
|
Dear @thevar1able, the PR is not updated for 1d0h58m44s. Please, either resolve the conflicts, or close it to finish the backport process of #85734 |
|
Dear @thevar1able, the PR is not updated for 1d1h4m7s. Please, either resolve the conflicts, or close it to finish the backport process of #85734 |
Original pull-request #85734
Do not merge this PR manually
This pull-request is a first step of an automated backporting.
It contains changes similar to calling
git cherry-picklocally.If you intend to continue backporting the changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.
The check results does not matter at this step - you can safely ignore them.
Troubleshooting
If the conflicts were resolved in a wrong way
If this cherry-pick PR is completely screwed by a wrong conflicts resolution, and you want to recreate it:
pr-cherrypicklabel from the PRYou also need to check the Original pull-request for
pr-backports-createdlabel, and delete if it's presented thereThe PR source
The PR is created in the CI job