Comment #6 on issue 739 by [email protected]: Determine what configuration
changes must be fully distributed before finishing the call
http://code.google.com/p/ganeti/issues/detail?id=739
Additional fix in:
commit 191dff7f924fdd4859fff39519da9bc2b0d9e696
Author: Petr Pudlak <[email protected]>
Date: Thu May 29 16:20:45 2014 +0200
Ensure full configuration distribution if MCs change
If a node is removed from the list of master candidates, we want to make
sure that after the operation the configuration will not be distributed
to the node any more. Without requiring full distribution, it's possible
that the node still receives configuration update from a previous call.
Also include the master node(s).
(While this shouldn't change without master failover, if it does, it's
definitely a good idea to flush the configuration.)
Signed-off-by: Petr Pudlak <[email protected]>
Reviewed-by: Klaus Aehlig <[email protected]>
--
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
