PhanLe1010
## Test live migration on Harvester deployment Test VM migration on Harvester and make sure that it is working as expected. REf: https://docs.harvesterhci.io/v1.0/vm/live-migration/
# Test Plan 1. [Test basic](https://github.com/longhorn/longhorn/issues/3715#issuecomment-1572664073) 2. [Attachment interruption](https://github.com/longhorn/longhorn/issues/3715#issuecomment-1558076675) 1. [Test Upgrade](https://github.com/longhorn/longhorn/issues/3715#issuecomment-1562305097) 1. [Test live migration on Harvester deployment](https://github.com/longhorn/longhorn/issues/3715#issuecomment-1563637065)
## Test basic ### Test UI 1. Test attach/detach volume using UI in normal/maintenance mode 1. Create deployment using Longhorn volume. Force detach the volume using Longhorn UI. Verify that...
@yangchiu I just double checked and it seems working. The UI should sends attach request with `attachmentID = "longhorn-ui"` in the first place. Maybe `attachmentID = ""` is left over...
> We recently experienced a problem that can be take note here: we get a power of death of the entire cluster, when it is power on again, we see...
## Test Plan: ### Crash volumes 1. Create a deployment using Longhorn volume 1. Write some data to the Longhorn volume's mount point and calculate the checksum 1. Crash all...
Hi @bauerjs1 I see in support bundle that Longhorn is using storage at mount point `/var/lib/longhorn/`. What is the filesystem at the mount point `/var/lib/longhorn/`. Is it ext4 or xfs?
Looks like it is `filesystemType: ext2/ext3` from the support bundle. You can not create a volume bigger than 2TB https://en.wikipedia.org/wiki/Ext3#:~:text=system%20may%20not.-,Size%20limits,-%5Bedit%5D if the host filesystem is ext2/ext3. You can use xfs...
> @PhanLe1010 Do you think we should mention and explain [#7924 (comment)](https://github.com/longhorn/longhorn/issues/7924#issuecomment-1944541060) in the [volume creation doc](https://longhorn.io/docs/1.6.0/nodes-and-volumes/volumes/create-volumes/)? I agree, it would be great. Also, maybe we can turn the log...
Hi @mantissahz , > Will it be flooding if we turn the log level up for this log? we already flush the log `level=error msg="There's no available disk for replica...