Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: pulsar scale-in failed #1380

Merged
merged 1 commit into from
Dec 30, 2024

Conversation

shanshanying
Copy link
Contributor

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (587e361) to head (c2a70b3).

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1380   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files         69      69           
  Lines       6685    6685           
=====================================
  Misses      6685    6685           

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

@shanshanying shanshanying merged commit af17f8a into main Dec 30, 2024
19 checks passed
@shanshanying shanshanying deleted the bugfix/pulsar-bookies-scale-in-failed branch December 30, 2024 06:14
@shanshanying
Copy link
Contributor Author

/cherry-pick release-1.0-beta

@apecloud-bot
Copy link
Collaborator

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

apecloud-bot pushed a commit that referenced this pull request Dec 30, 2024
(cherry picked from commit af17f8a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG]scale-in is always running after scale-out of pulsar cluster
5 participants