This tag is a catch-all for Puppet tasks that don't align with Puppet-Core, Puppet-Infrastructure, or Puppet CI. It is not specifically assigned to any team and can be used by any team to conveniently tag Puppet-related tasks.
See also:
This tag is a catch-all for Puppet tasks that don't align with Puppet-Core, Puppet-Infrastructure, or Puppet CI. It is not specifically assigned to any team and can be used by any team to conveniently tag Puppet-related tasks.
See also:
The series of patch has led to the removal of umask from git::clone
Change #927986 merged by Elukey:
[operations/puppet@production] git: remove umask from git::clone
Change #1056985 merged by Elukey:
[operations/puppet@production] cumin: set git::clone umask to match requested file mode
Change #1057815 merged by Slyngshede:
[operations/puppet@production] P:openldap::management Unbreak cross-validate-accounts script.
Change #1057815 had a related patch set uploaded (by Slyngshede; author: Slyngshede):
[operations/puppet@production] data.yaml Unbreak cross-validate-accounts script.
Change #1056985 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] cumin: set git::clone umask to match requested file mode
Change #1056981 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] cumin: clone homer public repo with default parameters
Change #927986 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] git: remove umask from git::clone
Thank you @Clement_Goubert ! Makes sense to me, I'll adjust the task accordingly
I think the mediawiki-config check is still needed since we're building the image with that repo copy on the deployment server.
Change #1056201 merged by Elukey:
[operations/puppet@production] puppetmaster: set git::clone umask to match requested file mode
Change #1056201 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] puppetmaster: set git::clone umask to match requested file mode
Change #1054892 merged by Andrea Denisse:
[operations/puppet@production] grafana: clone grafana-grizzly with default parameters
Change #1054890 merged by Arturo Borrero Gonzalez:
[operations/puppet@production] openstack: remove OpenTofu git::clone file mode
Change #1054889 merged by Btullis:
[operations/puppet@production] statistics: remove git::clone file mode
Change #1054892 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] grafana: clone grafana-grizzly with default parameters
Change #1054890 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] openstack: remove OpenTofu git::clone file mode
Change #1054889 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] statistics: remove git::clone file mode
I got another error at backup2002 (es5):
2024-06-26 17:07:31 [ERROR] - Could not read data from enwiki.blobs_cluster27: Lost connection to MySQL server during query
This seems to not be reproducible, maybe it was related to cold caches after reboot? Lowering the priority as not happening again since, but wanting to trace it at some point.
How about adding a MAILTO to the timer and mail a specific list / team / group? I think that alerting via IRC is becoming less reliable and direct email would be more effective. (or even automatic ticket creation)
I think the last step to do here is to validate that any rsync failures will get reported on IRC. Then we can consider all the immediate followups of this incident done, and more slowly continue on with the larger work at T367119: Install a default timeout for systemd::timer::jobs.
One other option: Add a separate wrapper define systemd::timer::job_capped which has the timeout as a mandatory argument (but without a default). And then reach out to SRE teams to migrate the jobs based what the respective uses cases needed.
Alternatives to consider:
Change #1041760 merged by CDanis:
[operations/puppet@production] puppetserver syncs: also add monitoring + timeout
Change #1041760 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/puppet@production] puppetserver syncs: also add monitoring + timeout
Change #1041217 merged by CDanis:
[operations/puppet@production] enable monitoring+logging for puppetmaster syncs
Change #1041217 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/puppet@production] enable monitoring+logging for puppetmaster syncs