PhanLe1010

> @PhanLe1010, do we still need to deal with this one? Do you think it was unintentionally resolved by [longhorn/longhorn-manager#1942](https://github.com/longhorn/longhorn-manager/pull/1942)? Yeah, the ticket https://github.com/longhorn/longhorn-manager/pull/1942 resolved the duplicated snapshot concern. And...

# Test plan: Case 1: Clone retry 1. Create PVC a volume of 5G with 1 replica 1. Attach the volume. Write 4G data into it. Calculate the checksum of...

@c3y1huang Looks like the creation of `longhorn-engine-manager` and `longhorn-replica-manager` headless service is to fix this security issue https://github.com/longhorn/security/issues/2 . It is a hotfix while the better fix is using mtls....

## Test Plan 1. Install Longhorn v1.6.2 using Helm 1. See that there are longhorn-engine-manager and longhorn-replica-manager services 1. Upgrade Longhorn to master-head 1. Verify that there are no longhorn-engine-manager...

@docbobo Quick question, was this Longhorn installation ever on version 1.4.x?

Oh. I found a SystemBackup CR with version v1.4.2 so it is is `yes` for the above question ```yaml apiVersion: v1 items: - apiVersion: longhorn.io/v1beta2 kind: SystemBackup metadata: creationTimestamp: "2024-04-26T20:38:27Z"...

Can I have another question? Has you ever upgraded this Longhorn instance to 1.5.x? @docbobo

Because we already have support bundle, we can investigate in the background. In the meantime, can you try this workaround to see if you can get out of the stuck...

OK. I think we have a good idea of the root cause. Will post it shortly

Are you sure that you edited the replicas @docbobo ? I see that the replica `pvc-2064afaf-8de8-48e4-959d-188ed2dd99b3-r-7d718685` has `spec.revisionCounterDisabled: false` in the newest support bundle that you sent.