After updating the redis backend in 1294279, I ran puppet
2026-06-09T08:17:41.926893+00:00 registry2005 puppet-agent[1970984]: (/Stage[main]/Docker_registry/Service[docker-registry]) Triggered 'refresh' from 3 events
However the services, docker-registry-ha-jwt.service, docker-registry-swift.service, docker-registry-ml.service, docker-registry-restricted.service, were not restrarted (or they were reloaded yet ignored it)
Eventually, I restarted them manually according to the docs
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| docker_registry::instance: proper restart when the config changes | Elukey | operations/puppet | production | +1 -1 |
Is this change on code owned by us or by Infrastructure Foundations? @Clement_Goubert do you know?
Change #1341249 had a related patch set uploaded (by Elukey; author: Elukey):
[operations/puppet@production] docker_registry::instance: proper restart when the config changes
Thanks for the report! In theory https://gerrit.wikimedia.org/r/c/operations/puppet/+/1341249 should fix the issue, restarting the instance-specific docker distribution rather than the generic one (that we don't use anymore in theory).
Change #1341249 merged by Elukey:
[operations/puppet@production] docker_registry::instance: proper restart when the config changes