Lanayx opened a new issue #6127: Broker can't start with 2.5.0 helm release URL: https://github.com/apache/pulsar/issues/6127 **Describe the bug** The broker is stuck in _CrashLoopBackOff_ on both minikube and google cloud with the same errors. **To Reproduce** Steps to reproduce the behavior: 1. use helm template with values-mini.yaml 2. set the following ``` # Pulsar proxy proxy: yes # Bookkeeper auto-recovery autoRecovery: no # Pulsar dashboard # Deprecated # Replace pulsar-dashboard with pulsar-manager dashboard: no # pulsar manager pulsar_manager: yes # Bastion pod for administrative commands bastion: yes # Monitoring stack (prometheus and grafana) monitoring: no ``` 3. set zookeeper, bookeeper, broker, proxy replicaCount to 1 4. See error (attached both logs for bookeeper and broker) **Expected behavior** Broker can be started normally **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - Helm: minikube and google cloud **Additional context** Attaching broker and bookeeper logs [bookeeper.log](https://github.com/apache/pulsar/files/4100280/bookeeper.log) [broker.log](https://github.com/apache/pulsar/files/4100281/broker.log)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
