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:
Details
Details
Description
Mon, Aug 26
Mon, Aug 26
joanna_borun triaged T371980: Puppet git::clone should default mode to 0644 (read-only) instead of 0755 as Low priority.
Wed, Aug 7
Wed, Aug 7
The series of patch has led to the removal of umask from git::clone
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #927986 merged by Elukey:
[operations/puppet@production] git: remove umask from git::clone
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1056985 merged by Elukey:
[operations/puppet@production] cumin: set git::clone umask to match requested file mode
Jul 29 2024
Jul 29 2024
Maintenance_bot removed a project from T371221: Single member group breaks cross validation script: Patch-For-Review.
gerritbot added a comment to T371221: Single member group breaks cross validation script.
Change #1057815 merged by Slyngshede:
[operations/puppet@production] P:openldap::management Unbreak cross-validate-accounts script.
gerritbot added a project to T371221: Single member group breaks cross validation script: Patch-For-Review.
gerritbot added a comment to T371221: Single member group breaks cross validation script.
Change #1057815 had a related patch set uploaded (by Slyngshede; author: Slyngshede):
[operations/puppet@production] data.yaml Unbreak cross-validate-accounts script.
Jul 25 2024
Jul 25 2024
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
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
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1056981 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] cumin: clone homer public repo with default parameters
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #927986 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] git: remove umask from git::clone
fgiunchedi renamed T370530: Clean up "git repo needs merge" checks from Port or delete "git repo needs merge" icinga check to Clean up "git repo needs merge" checks.
fgiunchedi added a comment to T370530: Clean up "git repo needs merge" checks.
Thank you @Clement_Goubert ! Makes sense to me, I'll adjust the task accordingly
Clement_Goubert added a comment to T370530: Clean up "git repo needs merge" checks.
I think the mediawiki-config check is still needed since we're building the image with that repo copy on the deployment server.
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1056201 merged by Elukey:
[operations/puppet@production] puppetmaster: set git::clone umask to match requested file mode
Jul 23 2024
Jul 23 2024
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
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
Jul 22 2024
Jul 22 2024
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054892 merged by Andrea Denisse:
[operations/puppet@production] grafana: clone grafana-grizzly with default parameters
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054890 merged by Arturo Borrero Gonzalez:
[operations/puppet@production] openstack: remove OpenTofu git::clone file mode
Jul 19 2024
Jul 19 2024
Jul 18 2024
Jul 18 2024
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054889 merged by Btullis:
[operations/puppet@production] statistics: remove git::clone file mode
Jul 17 2024
Jul 17 2024
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054892 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] grafana: clone grafana-grizzly with default parameters
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054890 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] openstack: remove OpenTofu git::clone file mode
gerritbot added a project to T338277: Puppet git::clone probably does not need `umask` parameter: Patch-For-Review.
gerritbot added a comment to T338277: Puppet git::clone probably does not need `umask` parameter.
Change #1054889 had a related patch set uploaded (by Hashar; author: Hashar):
[operations/puppet@production] statistics: remove git::clone file mode
Jun 27 2024
Jun 27 2024
• jcrespo raised the priority of T367882: Possible weird interaction between es backups and puppet runs leading to failures from Low to Medium.
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
Jun 26 2024
Jun 26 2024
• jcrespo triaged T367882: Possible weird interaction between es backups and puppet runs leading to failures as Low priority.
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.
Jun 18 2024
Jun 18 2024
Dzahn added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
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)
• jcrespo updated the task description for T367882: Possible weird interaction between es backups and puppet runs leading to failures.
CDanis added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
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.
Jun 17 2024
Jun 17 2024
joanna_borun edited projects for T367028: systemd-timer-mail-wrapper should not send mail as [email protected] from Cloud VPS, added: Puppet; removed Puppet-Core, Infrastructure-Foundations.
MoritzMuehlenhoff added a comment to 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.
CDanis added a comment to T367119: Install a default timeout for systemd::timer::jobs.
Alternatives to consider:
- Make this a required field instead of adding a default [harder up-front but potentially safer]
- Make omitting this field wmf puppet style guide violation [slower version of the above]
Jun 11 2024
Jun 11 2024
gerritbot added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
Change #1041760 merged by CDanis:
[operations/puppet@production] puppetserver syncs: also add monitoring + timeout
gerritbot added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
Change #1041760 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/puppet@production] puppetserver syncs: also add monitoring + timeout
gerritbot added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
Change #1041217 merged by CDanis:
[operations/puppet@production] enable monitoring+logging for puppetmaster syncs
Jun 10 2024
Jun 10 2024
gerritbot added a comment to T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).
Change #1041217 had a related patch set uploaded (by CDanis; author: CDanis):
[operations/puppet@production] enable monitoring+logging for puppetmaster syncs
CDanis updated the task description for T367113: Puppetmaster volatile data not synced to all puppet frontends for a month and a half (2024-04-27 to 2024-06-10).