Skip to content

fix: [BUG] [make compose up failed] panic: failed to start tenant "cozeloop" - #624

Open
Roshan931 wants to merge 1 commit into
coze-dev:mainfrom
Roshan931:prilog/fix-error-rocketmq-init-container-reports-success-08-21-2026-442635
Open

fix: [BUG] [make compose up failed] panic: failed to start tenant "cozeloop"#624
Roshan931 wants to merge 1 commit into
coze-dev:mainfrom
Roshan931:prilog/fix-error-rocketmq-init-container-reports-success-08-21-2026-442635

Conversation

@Roshan931

Copy link
Copy Markdown

Fixes #515

Root cause

RocketMQ init container reports success even when topic creation fails

Changes

  • Made the RMQ bootstrap init script fail loudly instead of silently: per-topic background jobs are now waited on individually so any failure sets a non-zero exit, mutating mqadmin calls (updateTopic/updateSubGroup) are retried up to 3 times, and a final verification asserts every configured topic is present in the namesrv topic list before the init container reports completion. Mirrored identically in the docker-compose and Helm bootstrap copies.

@CLAassistant

CLAassistant commented Aug 21, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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] [make compose up failed] panic: failed to start tenant "cozeloop"

2 participants