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

[BUG]The pulsar cluster is always in Creating status #8787

Open
tianyue86 opened this issue Jan 10, 2025 · 0 comments
Open

[BUG]The pulsar cluster is always in Creating status #8787

tianyue86 opened this issue Jan 10, 2025 · 0 comments
Assignees
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Milestone

Comments

@tianyue86
Copy link

Describe the env
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.22
kbcli: 1.0.0-beta.9

To Reproduce
Steps to reproduce the behavior:

  1. Create pulsar cluster with yaml below
    pulnew.yaml.txt

  2. Check the status:

k get cluster -A|grep pul
default     pulsar-tmpegf     pulsar               DoNotTerminate       Creating   25m

k get pod|grep pul
pulsar-tmpegf-bookies-recovery-0   0/1     Init:0/1           0                 22m
pulsar-tmpegf-zookeeper-0          1/1     Running            0                 22m
pulsar-tmpegf-zookeeper-1          1/1     Running            0                 22m
pulsar-tmpegf-zookeeper-2          1/1     Running            0                 22m

k get cmp|grep pul
pulsar-tmpegf-bookies-recovery   pulsar-bookies-recovery-3-1.0.0-alpha.0   3.0.2             Creating   26m
pulsar-tmpegf-zookeeper          pulsar-zookeeper-3-1.0.0-alpha.0          3.0.2             Running    26m
  1. describe pod
Events:
  Type    Reason          Age   From               Message
  ----    ------          ----  ----               -------
  Normal  Scheduled       17m   default-scheduler  Successfully assigned default/pulsar-tmpegf-bookies-recovery-0 to cn-zhangjiakou.10.0.0.140
  Normal  AllocIPSucceed  17m   terway-daemon      Alloc IP 10.0.0.10/24 took 28.468324ms
  Normal  Pulled          17m   kubelet            Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/pulsar:3.0.2" already present on machine
  Normal  Created         17m   kubelet            Created container check-bookies
  Normal  Started         17m   kubelet            Started container check-bookies
  1. Logs
    There is no obvious error in log.
    report-cluster-pulsar-tmpegf-2025-01-10-15-57-51.zip

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Jan 10, 2025
@tianyue86 tianyue86 added this to the Release 1.0.0 milestone Jan 10, 2025
@github-actions github-actions bot modified the milestones: Release 1.0.0, Release 0.9.3 Jan 14, 2025
@tianyue86 tianyue86 added the severity/major Great chance user will encounter the same problem label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Projects
None yet
Development

No branches or pull requests

2 participants