davidtclin58

Results 68 comments of davidtclin58

During the upgrade process from v1.2.1 to v1.2.2-rc2 on 3 nodes kvm machines. Encounter the issue #5712 , the upgrade stuck in upgrading system service ![image](https://github.com/harvester/harvester/assets/29251855/53b1beb5-b792-4241-9b99-65b49baf1d88) Try to create another...

Verifing on `v1.2.2-rc2` (24/05/03). ### Result #### Two nodes environment $\color{green}{\textsf{PASS}}$ On first node: ensure the images that are going to be removed after upgrade no longer exists $~~$ 1....

Validate this issue on `provo environment` to check whether it still happen under system with enough cpu/memory resources. ### Result After upgrade from v0.3.0 to v1.0.0 GA on provo bare...

Thanks for the checking, according to previous comment, we would move the issue to ready for testing and test til the rke2 have been bumped for the upcoming release.

Verify **failed** on `master-d3dc81ca-head` (24/01/04) with Rancher `v2.7.9` The original upgrade icon disappear issue did not happen, while we encounter a new UI display issue during the test. Thus we...

Tested the issue when reload the page in Rancher virtualization management, the upgrade icon would disappear On Rancher `v2.8.1` and `v2.7.9` with Harvester `v1.3.0-rc1`, we can reproduce this issue https://github.com/harvester/harvester/assets/29251855/8f7eafaa-6df3-43df-9084-09d17cb7430b...

Verifying on `v1.3-50a00ad1-head` (24/02/21). ### Result $\color{green}{\textsf{PASS}}$ VM status after power off then power on node machine after 12 hours $~~$ * All vm display `running` state after power on...

When I restart the node machine, after node restart: * All vm stuck in `Starting` state ![image](https://github.com/harvester/harvester/assets/29251855/caf200d0-c5a7-4c2f-9958-6b23334adf67) ![image](https://github.com/harvester/harvester/assets/29251855/a1446457-464e-4398-8f2f-4c756a956057) * Check the vmi state kept in Scheduling ``` harv13-240221:~ # kubectl...

While checking issue #5109, follow the [steps](https://github.com/harvester/harvester/issues/5109#issue-2119476374) to reproduce issue. After configure the storage class and create a virtual machine. * The virtual machine keep in `Starting` state ![image](https://github.com/harvester/harvester/assets/29251855/44384d2c-abef-43dc-86e9-692b3f4cbd5d) *...

While we encounter issue while restarting node would cause all VMs in `Starting` state in [test result](https://github.com/harvester/harvester/issues/4033#issuecomment-1963336920) for issue #4633 And encounter issue can't create VM while configured storage network...