PhanLe1010

Hi @cmhdave @nazarewk Could you please send us a support bubble to `[email protected]` for investigation?

@nazarewk You mentioned in [Slack](https://rancher-users.slack.com/archives/CC2UQM49Y/p1713898026100959) that > looks like it's flipping between 2 versions of certificates back and forth > the ONLY difference between them is certificate serial number I...

@soilidokay Can I have more details? So you deploy the yaml ``` apiVersion: v1 kind: PersistentVolumeClaim metadata: name: longhorn-volv-pvc spec: accessModes: - ReadWriteOnce storageClassName: longhorn resources: requests: storage: 2Gi ---...

@mantissahz Do we have any update on this ticket?

@mantissahz The logs look as if some instance-manager pod crash to me. Btw, for the multi-attach error at https://github.com/longhorn/longhorn/issues/7313#issuecomment-1850177401. Are you still having the issue @CaptainKrby ? If yes, can...

> However, how can I patch all my volumes and ensure that this does not happen again in the future? Hi @CaptainKrby We would like to investigate. Did you recently...

Thanks @CaptainKrby for the update! I will try to reproduce this issue in lab. What is the yaml of one of your typical workload?

Hi @EStork09 @CaptainKrby More data to reproduce would be great. Like: 1. Deploy Longhorn version xxx 1. Deploy workload, chart yyy . I know @CaptainKrby provided bitnami/kafka but is there...

We will investigate this ticket in https://github.com/longhorn/longhorn/issues/8339

Sounds good to me. Should we add this ticket to planing? @derekbit @innobead TODO: If we decide to keep the failed pre-upgrade job pod, we also need to make sure...