PhanLe1010

Thanks @simsicon How about `kubectl get nodes.longhorn.io node1 -n longhorn-system -o yaml`?

@simsicon There is another setting that controls the disk scheduling, the picture below. You can low it down to make the disk schedulable By the way, it seems that there...

> MountVolume.Setup failed while expanding volume for volume "pvc-3cc715b2-aaa2-4c1d-a788-ffc71905874c" : Expander.NodeExpand found CSI plugin kubernetes.io/csi/driver.lon │ │ ghorn.io to not support node expansion Why does Kubelet want to expand this...

Ok. It seems that the filesystem has not been appropriately resized. I would have to review[ the expansion flow](https://github.com/longhorn/longhorn-manager/blob/8c7c215f0e10b23dff5cad2d0563494478a769d0/csi/controller_server.go#L820) from the code perspective to determine the root cause

@amnk Do you mean deploying this service monitoring CR with Longhorn by default? https://longhorn.io/docs/1.1.2/monitoring/integrating-with-rancher-monitoring/#add-longhorn-metrics-to-the-rancher-monitoring-system It would mean that Longhorn also must be shipped with `ServiceMonitor` CRD depending on where user...

Thanks @amnk and @ybykov-a9s for the feedback. We will discuss this proposal with the team cc @joshimoo @shuo-wu @innobead. Do you have any opinion on this? I agree with users...

@schnapsidee Thank you for reporting In order to help us to investigate, could you send Longhorn support bundle to `[email protected]`. Is it correct that the backup name is `backup-dbb8cedbc1b049d9` and...

> level=debug msg=\"Requeue backup-dbb8cedbc1b049d9 due to conflict\" backup=backup-dbb8cedbc1b049d9 controller=longhorn-backup error=\"Operation cannot be fulfilled on backups.longhorn.io \\\"backup-dbb8cedbc1b049d9\\\": the object has been modified; please apply your changes to the latest version and...

> It seems that the log in the Longhorn system is too large and there is something wrong with this log collection feature... When the progress pass 20%, we are...

From the code, look like the job will still shows as completed even if the backup/snapshot fails: https://github.com/longhorn/longhorn-manager/blob/9e639a08c8c6c0b520bd5b1e6a3792406fa75dd4/app/recurring_job.go#L187-L191 Is this intentional, cc @c3y1huang ?