Status: Started
Owner: [email protected]
Labels: Type-Defect Priority-High Milestone-Release2.12 Component-wconfd
New issue 1115 by [email protected]: When doing master failover, there is a
race between starting WConfd and updating the configuration
https://code.google.com/p/ganeti/issues/detail?id=1115
What steps will reproduce the problem?
1. Run master failover on a master candidate
What is the expected output? What do you see instead?
Occasionally it happens that the temporary WConfd instance on the new
master doesn't start fast enough and the request for updating the
configuration fails.
And since we're not running on the master node, the Transport class doesn't
retry. The proper fix is to modify this particular call so that the
Transport class properly retries, even if not on the master node.
--
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
