Updates:
Status: NeedFeedback
Comment #2 on issue 613 by [email protected]: Incorrectly offlined node leads
to instances running on secondary node
http://code.google.com/p/ganeti/issues/detail?id=613
I have some trouble reproducing this issue on both 2.6 and on master.
The two commands used (offline node, failover) produce the same warnings
until the preparation of the disk on the secondary, which succeeds as
expected on my cluster. I experimented with a different number of instances
and disks of varying size (only up to 25G as in the log though). According
to your output, we share the same version of DRBD as well.
Is there some other information you can supply regarding how the cluster is
set up, or how the nodes were added or instances created?
Despite the command succeeding, the cluster is still left in a somewhat
strange state with gnt-cluster verify failing after a re-add. Looking into
this now.
--
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
