Updates:
Status: Fixed
Comment #4 on issue 1114 by [email protected]: binding RAPI to a specific
IP makes the cron watcher unhappy
https://code.google.com/p/ganeti/issues/detail?id=1114
Fixed in 2.12 with:
commit fbf8089c7f19d6c4d9844d00d2f25a71f644a5b0
Author: Helga Velroyen <[email protected]>
Date: Thu Jul 2 13:38:17 2015 +0200
Watcher: add option for setting RAPI IP
Per default, the RAPI daemon binds to 0.0.0.0 when being
started. This means it serves from any IP the machine is
configured for. This works well together with the watcher
which always polls the RAPI daemons on 127.0.0.1 and
restarts it when it is not reachable.
If a user decides to start the RAPI daemon with a particular
IP other than 127.0.0.1 (using the option -b, for example
set in /etc/default/ganeti), RAPI will only serve from that
IP and thus it will not be reachable from 127.0.0.1. Since
the watcher only polls on this IP, it will inevitably fail
to connect to the RAPI daemon and thus restart it every five
minutes.
To solve this, this patch adds an option --rapi-ip to the
watcher. Whenever -b of the RAPI daemon is set, the watcher
needs to be fed the same IP with --rapi-ip (which means
editing /etc/cron.d/ganeti for example). This is not optimal
regarding user experience (as it is easy to forget one of
the two places), but the alternative would be to make this
a ganeti configuration parameter which is fed to both, RAPI
daemon and watcher, but this would be significantly more
effort for this relatively rarely used feature.
Signed-off-by: Helga Velroyen <[email protected]>
Reviewed-by: Petr Pudlak <[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
