Open Nuttymoon opened 2 years ago
Thank you for reporting this. We will look into this.
I really don't consider this a bug... It may be useful to add... but I think that this would result in a lot of confusion if a VM is currently being used, but is no longer the same version... We could shutdown the blockchain and restart it with the new VM version... but I feel like at that point we should just be restarting the node.
This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen
label will cause this issue to ignore lifecycle events.
Describe the bug After upgrading a VM to a newer version, the API call
admin.loadVMs
do not detect the change, leaving the VM in the old version.To Reproduce
info.getNodeVersion
plugins
directory with another versionadmin.loadVMs
: API return is emptyinfo.getNodeVersion
, notice that VM version is unchangedExpected behavior To minimize node downtime,
admin.loadVMs
should be able to detect a version change and reload the VMs that have indeed changed.Screenshots (I am using symlinks in the
plugins
directory)info.getNodeVersion
result (there is a version display bug for the Subnet EVM but see below that version0.1.1
is linked):plugins
folderadmin.loadVMs
result is empty:info.getNodeVersion
result is unchangedinfo.getNodeVersion
returns:Operating System Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-104-generic x86_64)
By submitting this issue I agree to the Terms and Conditions of the Developer Accelerator Program.