Status: New
Owner: ----
New issue 1200 by [email protected]: gnt-instance failover
--ignore-consistency does not work for extstorage
https://code.google.com/p/ganeti/issues/detail?id=1200
Hi
ganeti 2.15 (2.15.2-1~gdn7+1, Debian package)
Disks ONLY by extstorage
Situation:
Multi Node cluster, loads of VMs.
One Node dies, had some VMs on it.
How to get them running elsewhere? manpage of gnt-instance suggests using
gnt-instance failover --ignore-consistency $VM
Except thats broken:
Wed Jan 11 12:52:00 2017 Failover instance lvm-test-02ct
Wed Jan 11 12:52:00 2017 * checking disk consistency between source and
target
Wed Jan 11 12:52:00 2017 * shutting down instance on source node
Wed Jan 11 12:52:03 2017 - WARNING: Could not shutdown instance
lvm-test-02ct on node bl32c04, proceeding anyway; please make sure node
bl32c04 is down; error details: Error 7: Failed connect to 10.28.5.25:1811;
No route to host
Wed Jan 11 12:52:03 2017 * closing instance disks on node bl32c04
Failure: command execution error:
Cannot close instance disks on node bl32c04: Error 7: Failed connect to
10.28.5.25:1811; No route to host
Yes, of course the node is down, I just told it to ignore consistency
problems, this should include NOT failing when one can not close the
instance disks.
The workaround, also I think its wrong to do so, is using
gnt-instance modify --new-primary othernode lvm-test-02ct
which will spit out some warnings, but then modify the vm data, after with
the instance can be started again. But it would be much better and way more
consistent if gnt-instance could handle this.
Greetings
Joerg
--
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
