This message was deleted.
# harvester
a
This message was deleted.
s
It now says
virt-launcher pod has not yet been scheduled
but trying to update the storage network still errors with it thinking a VM is running.
I cloned the VM and deleted the original, and then was able to set the Storage Network without error.
r
Did you shut down the VM from its OS or using the Harvester UI?
This is actually a potential enhancement for Harvester. I’ve created an issue tracking it. https://github.com/harvester/harvester/issues/4363 Feel free to add some comments to the issue if you find anything worth mentioning. Thanks for finding this and making Harvester better!
s
I had shut it down from the OS. It was Ubuntu and I issued the command
shutdown now -h
. Now I’m wondering if it was the
-h
halt flag that left the VM in a weird state.
Ah, I just read over the issue you created. That makes sense now and is exactly what I experienced. Thank you for opening that issue.
🙌 1