Re: [I] Zookeeper SSL Failures When Certificate Is Rolled [pulsar-helm-chart]

["beelis (via GitHub)" <gi...@apache.org>]

beelis commented on issue #359:
URL: https://github.com/apache/pulsar-helm-chart/issues/359#issuecomment-2582120929

   Same issue with version 3.7.0 (pulsar 4.0.0). After a restart of all pulsar pods, the zookeeper could recover. 
   
   After that, the pulsar functions were not able to connect to the broker, they also seem to have the old cert cached:
   
   `2025/01/10 08:31:36.353 asm_amd64.s:1700: [info] Connecting to broker remote_addr=pulsar+ssl://pulsar-broker:6651
   2025/01/10 08:31:36.368 asm_amd64.s:1700: [warning] Failed to connect to broker. error=tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-01-10T08:31:36Z is after 2025-01-05T18:12:06Z remote_addr=pulsar+ssl://pulsar-broker:6651`
   
   Restarting the pulsar function pod did not help, only a redeploy of the function solved the problem.
   
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org