Restoration of a VM snapshot on a remote node fails. When the headnode flag is used for remote minimega instances which appears to be the default, the remote nodes try to obtain the snapshot disk image from the head node. Since the snapshot disk image is not on the head node, restoration of the VM on the remote node fails. One quick fix is to just override the default minimega deploy flags to exclude the headnode flag. While excluding the headnode flag will offer a quick fix, should minimega fail to restore a VM when the disk snapshot exists on the node hosting the VM? Should an alternative workflow exist for restoration of VM snapshots on remote nodes with the headnode flag? This might be a more appropriate issue for the minimega repository but since Phenix encapsulates the restoration of a VM, it seemed appropriate to also log the issue in the Phenix repository.
Restoration of a VM snapshot on a remote node fails. When the
headnodeflag is used for remote minimega instances which appears to be the default, the remote nodes try to obtain the snapshot disk image from the head node. Since the snapshot disk image is not on the head node, restoration of the VM on the remote node fails. One quick fix is to just override the default minimega deploy flags to exclude theheadnodeflag. While excluding theheadnodeflag will offer a quick fix, should minimega fail to restore a VM when the disk snapshot exists on the node hosting the VM? Should an alternative workflow exist for restoration of VM snapshots on remote nodes with theheadnodeflag? This might be a more appropriate issue for the minimega repository but since Phenix encapsulates the restoration of a VM, it seemed appropriate to also log the issue in the Phenix repository.