CC007

Results 145 comments of CC007

So no info about why it's failing or shutting down? What about the first time after I installed Longhorn 1.6.1, added nexus and then restarted the node? Did anything special...

Would any changes be needed to longhorn to properly diagnose the issue? If needed, I'd be down to rerun the test once these changes are added.

You can see that this pvc has a different from the one that was reported in #8091 . I had cleaned up all longhorn resources (including custom resources) in k8s...

Okay, I'll try again, just to sanity check **Uninstallation:** 1. In Rancher I uninstalled the Nexus helm chart, so that the volume wasn't needed anymore 2. In Longhorn I deleted...

> Did you delete the /var/lib/longhorn on the physical nodes or in Longhorn UI only. We shouldn't not delete it on the physical nodes since it contains some binary that...

As you can see, the snapshot that I created doesn't show up anymore too.

And then the replica on node 1-3 disappeared: ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/698b9dd7-3528-4d33-b195-80a63d07179c) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/6cde2522-a97e-4ba9-8339-c34ed842b9a1) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/cfccd629-f16a-45c3-ac3f-7cfaa0f186a5) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/fb48247a-a6d8-4b61-b38f-b6717219a67a) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/ea6c63ca-d89a-4ca5-8463-6dc541f190a8) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/13c37b88-5c73-4f65-809a-461be66bb464) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/3702c583-61b8-403b-a6c1-81651a6e1084) ![afbeelding](https://github.com/longhorn/longhorn/assets/5381337/92762511-d46f-4923-86fd-30d65e113456)

Here is the bundle after the last test: https://we.tl/t-eul6aOGIlJ

Also, the fact that the replicas get corrupted by a node reboot is one thing, but the fact that the snapshot is no longer available to revert back to in...

Any progress on the analysis of this bug?