On the new Sentinel-based Toolforge Redis cluster, Sentinel and Puppet both keep overwriting the config file and restarting the Redis service causing some disruption.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T289883 cloud-vps: actively deprecate/phase out use of Debian Stretch | |||
| Resolved | • taavi | T306099 Cloud VPS "tools" project Stretch deprecation | |||
| Resolved | • taavi | T306100 Cloud VPS "toolsbeta" project Stretch deprecation | |||
| Resolved | • taavi | T275864 Toolforge: migrate to Debian Buster or later | |||
| Open | None | T262350 bad failure cases for wmcs custom puppet enc | |||
| Resolved | • taavi | T267082 Rebuild Toolforge servers that should not have NFS mounted (and with affinity) | |||
| Resolved | • taavi | T278541 Toolforge: migrate redis servers to Debian Buster or later | |||
| Resolved | dcaro | T309014 sentinel and puppet overwriting toolforge redis config |
Event Timeline
Comment Actions
I'm looking at the puppetcode, trying to decouple the redis config from the sentinel one (maybe just setup redis if the
config is not there instead of on every run)
Ideas are welcome as usual :)
Comment Actions
Change 805823 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] P:toolforge::redis_sentinel: stop sentinel and puppet fighting
Comment Actions
Change 805823 merged by David Caro:
[operations/puppet@production] P:toolforge::redis_sentinel: stop sentinel and puppet fighting
Comment Actions
Change 805837 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] P:toolforge::redis_sentinel: stop sentinel and puppet fighting (try 2)
Comment Actions
Change 805837 merged by David Caro:
[operations/puppet@production] P:toolforge::redis_sentinel: stop sentinel and puppet fighting (try 2)