Status: New
Owner: ----
New issue 1181 by [email protected]: `gnt-instance migrate`
applies "--paused" option from `gnt-instance start`
https://code.google.com/p/ganeti/issues/detail?id=1181
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
# gnt-cluster --version
gnt-cluster (ganeti v2.12.4) 2.12.4
# gnt-cluster version
Software version: 2.12.4
Internode protocol: 2120000
Configuration format: 2120000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.12.4
# hspace --version
hspace (ganeti) version v2.12.4
compiled with ghc 7.6
running on linux x86_64
I'm using qemu as the only available HV in the cluster.
What distribution are you using?
Debian Jessie amd64
What steps will reproduce the problem?
1. Bring up an instance with the "--paused" option set (`gnt-instance
startup --paused yourvm`)
2. Connect to the instance's console, thereby unpausing it (`gnt-instance
console yourvm`; then detach using the configured escape sequence)
3. Migrate the instance to another node (`gnt-instance -f migrate yourvm`)
What is the expected output? What do you see instead?
I'd expect the migrated instance to be unpaused when its execution resumes
on the new node. Instead, the instance is being paused there - the
_initial_ state configuration from when first starting the instance is
being transferred during migration, instead of the instance's current state.
I do understand that this could be by design and actually intended - but if
so, the documentation should be updated to reflect this. On my ganeti
release, the manpage currently reads:
"The --paused option is only valid for Xen and kvm hypervisors. This pauses
the instance at the start of bootup, awaiting gnt-instance console to
unpause it, allowing the entire boot process to be monitored for debugging."
I think it should read something like this instead:
"The --paused option is only valid for Xen and kvm hypervisors. Setting it
pauses the instance right at the start of bootup, and right after migrating
the instance to another node. An instance can be unpaused by connecting to
its console via gnt-instance console. The --paused option allows the entire
boot process to be monitored for debugging."
Furthermore, as both types of behaviour (pausing after migration, as well
as resuming instantly after migration) could very well be desired, maybe
introducing a new option that extends "--paused"'s behaviour (to only pause
the instance right after bootup, but never implicitly after migration)
should be considered.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
