Skip to content

fix: restore ops is always Creating when the Point of time incorrect#10112

Merged
wangyelei merged 5 commits intomainfrom
bugfix/restore_ops_hang
Mar 31, 2026
Merged

fix: restore ops is always Creating when the Point of time incorrect#10112
wangyelei merged 5 commits intomainfrom
bugfix/restore_ops_hang

Conversation

@wangyelei
Copy link
Copy Markdown
Contributor

No description provided.

@wangyelei wangyelei requested a review from a team as a code owner March 30, 2026 09:25
@wangyelei wangyelei added pick-1.0 Auto cherry-pick to release-1.0 when PR merged pick-1.1 Auto cherry-pick to release-1.1 when PR merged labels Mar 30, 2026
@github-actions github-actions bot added the size/XS Denotes a PR that changes 0-9 lines. label Mar 30, 2026
@apecloud-bot
Copy link
Copy Markdown
Collaborator

Auto Cherry-pick Instructions

Usage:
  - /nopick: Not auto cherry-pick when PR merged.
  - /pick: release-x.x [release-x.x]: Auto cherry-pick to the specified branch when PR merged.

Example:
  - /nopick
  - /pick release-1.1

@wangyelei wangyelei requested a review from ldming as a code owner March 30, 2026 09:34
@github-actions github-actions bot added size/M Denotes a PR that changes 30-99 lines. and removed size/XS Denotes a PR that changes 0-9 lines. labels Mar 31, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 31, 2026

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.69%. Comparing base (4ec0147) to head (bfdc9f0).
⚠️ Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
pkg/operations/restore.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10112      +/-   ##
==========================================
+ Coverage   51.57%   51.69%   +0.12%     
==========================================
  Files         525      525              
  Lines       58243    58243              
==========================================
+ Hits        30036    30110      +74     
+ Misses      25239    25177      -62     
+ Partials     2968     2956      -12     
Flag Coverage Δ
unittests 51.69% <50.00%> (+0.12%) ⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@apecloud-bot apecloud-bot added the approved PR Approved Test label Mar 31, 2026
@wangyelei
Copy link
Copy Markdown
Contributor Author

/approved

@wangyelei wangyelei merged commit fa896bc into main Mar 31, 2026
41 checks passed
@wangyelei wangyelei deleted the bugfix/restore_ops_hang branch March 31, 2026 03:21
@github-actions github-actions bot added this to the Release 1.2.0 milestone Mar 31, 2026
@apecloud-bot
Copy link
Copy Markdown
Collaborator

/cherry-pick release-1.1

@apecloud-bot
Copy link
Copy Markdown
Collaborator

/cherry-pick release-1.0

@apecloud-bot
Copy link
Copy Markdown
Collaborator

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks/actions/runs/23778869987

@apecloud-bot
Copy link
Copy Markdown
Collaborator

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks/actions/runs/23778869925

apecloud-bot pushed a commit that referenced this pull request Mar 31, 2026
apecloud-bot pushed a commit that referenced this pull request Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved PR Approved Test pick-1.0 Auto cherry-pick to release-1.0 when PR merged pick-1.1 Auto cherry-pick to release-1.1 when PR merged size/M Denotes a PR that changes 30-99 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] PITR restore cluster will remain in the "creating" state indefinitely when the Point of time incorrect

4 participants