Make writeConfigAndUnlock retryable
Make writeConfigAndUnlock retryable

We have the built-in assumption that daemons can be restarted
at any time. This includes situations where an action is already
taken, but the caller did not get the answer jet. For the case
of writeConfigAndUnlock this can lead to the command being reissued;
of course, it should not do anything on second attempt, but fail in
a way the caller can live with.

Signed-off-by: Klaus Aehlig <4ce51de36d9068cd7db2eec1151e0f3f95419008@google.com>
Reviewed-by: Petr Pudlak <9d19625f8ee825a2c398462ed335cbcf98f79c32@google.com>

andir/ganeti,yiannist/ganeti,ganeti/ganeti,leshchevds/ganeti,mbakke/ganeti,ganeti/ganeti,dimara/ganeti,onponomarev/ganeti,andir/ganeti,bitemyapp/ganeti,grnet/snf-ganeti,yiannist/ganeti,ganeti/ganeti,mbakke/ganeti,bitemyapp/ganeti,onponomarev/ganeti,leshchevds/ganeti,dimara/ganeti,leshchevds/ganeti,yiannist/ganeti,grnet/snf-ganeti,andir/ganeti,mbakke/ganeti