Cherry pick #78541 to 25.3: s3queue: fix logical error "Cannot unregister: table uuid is not registered"#78868
Conversation
…annot-unregister s3queue: fix logical error "Cannot unregister: table uuid is not registered"
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h59m12s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h0m11s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d25h18m24s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h25m27s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h44m34s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h59m24s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h47m1s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h46m18s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h59m3s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d25h1m8s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h58m35s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h0m30s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d25h1m16s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h59m2s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h59m21s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h58m43s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d25h3m19s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h0m2s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h1m12s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h0m39s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d25h2m31s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h53m11s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
|
Dear @jkartseva, @kssenii, the PR is not updated for 1d24h0m11s. Please, either resolve the conflicts, or close it to finish the backport process of #78541 |
Original pull-request #78541
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.
Note
This pull-request will be merged automatically. Please, do not merge it manually (but if you accidentally did, nothing bad will happen).
Troubleshooting
If the PR was manually reopened after being closed
If this PR is stuck (i.e. not automatically merged after one day), check #78541 for
pr-backports-createdlabel and delete it.Manually merging will do nothing. The
pr-backports-createdlabel prevents the original PR #78541 from being processed.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 PR #78541 for
pr-backports-created, and delete if it's presented thereThe PR source
The PR is created in the CI job