Change #1093912 had a related patch set uploaded (by Zfilipin; author: Zfilipin):

[mediawiki/extensions/RelatedArticles@master] selenium: Replace Node.js Assert library with WebdriverIO Expect library

https://gerrit.wikimedia.org/r/1093912

adding our team tag for visibility

Cookbook cookbooks.sre.hosts.rename started by jayme@cumin2002 from kubernetes1007 to kubestage1005 completed:

• kubernetes1007 (PASS)
  • ✔️ Downtimed host on Icinga/Alertmanager
  • ✔️ Disabled puppet and its timer
  • ✔️ Disabled debmonitor-client timer
  • ✔️ Netbox updated
  • ✔️ BMC Hostname updated
  • ✔️ DNS updated
  • ✔️ Switch description updated
  • ✔️ Removed from DebMonitor
  • ✔️ Removed from Puppet master and PuppetDB
  • Rename completed 👍 - now please run the re-image cookbook on the new name with --new

I investigated this further. The wmf-quibble-core-vendor-mysql-php74 job (slow - 30 mins) actually runs the extensions suite, because --phpunit-testsuite=extensions is passed to Quibble for that job. Enabling parallel runs here should work without issue. For other jobs, for example mediawiki-quibble-vendor-mysql-php74 where the default suite is run, Quibble detects that the default suite is requested and falls back to a linear run - this is acceptable for now because the job only takes 10 mins as it is. We could look at a separate ticket to speed up mediawiki-quibble-vendor-mysql-php74 later.

Change #1093910 had a related patch set uploaded (by Zfilipin; author: Zfilipin):

[mediawiki/extensions/Echo@master] WIP selenium: Replace Node.js Assert library with WebdriverIO Expect library

https://gerrit.wikimedia.org/r/1093910

Change #1093909 had a related patch set uploaded (by Arthur taylor; author: Arthur taylor):

[integration/config@master] Enable PHPUnit parallel testing for mediawiki/core

https://gerrit.wikimedia.org/r/1093909

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2160.codfw.wmnet with OS bookworm completed:

• wikikube-worker2160 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211258_cgoubert_3728890_wikikube-worker2160.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

In T379885#10339053, @SD0001 wrote:

This occurs when votewiki invokes the origin wiki's action=securepollauth API to retrieve user details. The JSON response is supposed to include isSitewideBlocked which can be null, true or false. Error seems to indicate sometimes the property is not set at all.

Change #1093908 had a related patch set uploaded (by Isabelle Hurbain-Palatin; author: Isabelle Hurbain-Palatin):

[mediawiki/extensions/AbuseFilter@master] Replace uses of deprecated ParserOutput::getText()

https://gerrit.wikimedia.org/r/1093908

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2164.codfw.wmnet with OS bookworm completed:

• wikikube-worker2164 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211255_cgoubert_3729280_wikikube-worker2164.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

This doesn't seem to be related to the switchover of Wikifeeds or RESTBase Sunset. FWIW I'll move this to radar and add Content-Transform-Team-WIP for investigation.

Change #1092231 abandoned by Kosta Harlan:

[mediawiki/extensions/CentralAuth@master] (WIP) UserLogoutHookHandler: Don't modify injected_html for API responses

Reason:

Going a different route, T345819#10343777

https://gerrit.wikimedia.org/r/1092231

Change #1093864 merged by JMeybohm:

[operations/puppet@production] Reclaim kubernetes100[78] as kubestage100[56] 1/2

https://gerrit.wikimedia.org/r/1093864

Change #1093864 merged by JMeybohm:

[operations/puppet@production] Reclaim kubernetes100[78] as kubestage100[56] 1/2

https://gerrit.wikimedia.org/r/1093864

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2162.codfw.wmnet with OS bookworm completed:

• wikikube-worker2162 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211252_cgoubert_3729126_wikikube-worker2162.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2165.codfw.wmnet with OS bookworm completed:

• wikikube-worker2165 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211249_cgoubert_3729365_wikikube-worker2165.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

Change #1093907 had a related patch set uploaded (by Zfilipin; author: Zfilipin):

[mediawiki/extensions/AbuseFilter@master] WIP selenium: Replace Node.js Assert library with WebdriverIO Expect library

https://gerrit.wikimedia.org/r/1093907

In T95100#10343712, @stjn wrote:

In T95100#10343681, @Nikki wrote:

This is really annoying, how do I turn it off?

You probably mean the change in T377663: Support autocompletion in CodeEditor. CodeMirror 6 isn’t available anywhere other than mediawiki.org yet and I don't think autocompletion is there at all.

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2163.codfw.wmnet with OS bookworm completed:

• wikikube-worker2163 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211246_cgoubert_3729215_wikikube-worker2163.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2158.codfw.wmnet with OS bookworm completed:

• wikikube-worker2158 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211242_cgoubert_3728774_wikikube-worker2158.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

Change #1092229 abandoned by Kosta Harlan:

[mediawiki/core@master] (WIP) UserLogoutCompleteHook: Allow for returning data in ApiLogout

https://gerrit.wikimedia.org/r/1092229

Looks like the task type "administrative request" doesn't have story points field. @Aklapper Is that something you can fix?

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2161.codfw.wmnet with OS bookworm completed:

• wikikube-worker2161 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211239_cgoubert_3729032_wikikube-worker2161.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

Thanks, I agree that option 1 would be better. If the job status is the only other data to display, another option is to use CdxMessage to display it.

Once we do the switchover,

Cookbook cookbooks.sre.hosts.reimage started by cgoubert@cumin1002 for host wikikube-worker2156.codfw.wmnet with OS bookworm completed:

• wikikube-worker2156 (PASS)
  • Downtimed on Icinga/Alertmanager
  • Disabled Puppet
  • Removed from Puppet and PuppetDB if present and deleted any certificates
  • Removed from Debmonitor if present
  • Forced PXE for next reboot
  • Host rebooted via IPMI
  • Host up (Debian installer)
  • Add puppet_version metadata to Debian installer
  • Checked BIOS boot parameters are back to normal
  • Host up (new fresh bookworm OS)
  • Generated Puppet certificate
  • Signed new Puppet certificate
  • Run Puppet in NOOP mode to populate exported resources in PuppetDB
  • Found Nagios_host resource for this host in PuppetDB
  • Downtimed the new host on Icinga/Alertmanager
  • Removed previous downtime on Alertmanager (old OS)
  • First Puppet run completed and logged in /var/log/spicerack/sre/hosts/reimage/202411211236_cgoubert_3728713_wikikube-worker2156.out
  • configmaster.wikimedia.org updated with the host new SSH public key for wmf-update-known-hosts-production
  • Rebooted
  • Automatic Puppet run was successful
  • Forced a re-check of all Icinga services for the host
  • Icinga status is optimal
  • Icinga downtime removed
  • Updated Netbox data from PuppetDB

In T345819#10325629, @kostajh wrote:

In T345819#10325556, @kostajh wrote:

In T345819#10325529, @kostajh wrote:

I'm wondering if it's possible, though, to just use the headers for logout events. We'd have to somehow issue a redirect after the user clicks "Logout" in order to set the request headers for Accept-CH.

This seems like more trouble than it is worth, having looked at it a little bit just now.

For the JS API collection approach, CheckUser's onUserLogoutComplete can encode the user's ID and the insert ID in &$injected_html. Then the client hints JS code can use this to issue a POST request to the client hints REST endpoint.

@Tchanders If you think any of the changes you made to support unprotecting unintentionally protected filters are valuable to document, please feel free to update the task and add as necessary.

Here are the cases we know of:

• Parsoid cache - which is going to be migrated to ParserCache
• PCS cache - PCS will manage its own cache T348996: Change changeprops rules to pre-generate/invalidate cache directly to PCS rather than in restbase
• Mathoid cache - which is unknown what we are going to do with the future and we are waiting on developments of T271001: Transition to MathML rendering as default

TODO next:

• activate IPv6 support within openstack (merge https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/132)
• enable IPv6 on the edge network
• test everything
• generate docs T380054: Cloud VPS: prepare documentation on VXLAN/IPV6 migration
• update horizon settings T380081: horizon: enable the UI to select networks on VM creation panel

Change #1093905 had a related patch set uploaded (by EoghanGaffney; author: EoghanGaffney):

[operations/puppet@production] vrts: Block bondedsender RBL check from spamassassin on vrts

https://gerrit.wikimedia.org/r/1093905

Change #1092187 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] client hints: Collect on Special:UserLogout

https://gerrit.wikimedia.org/r/1092187

When a source string (en.json) is changed in the project, they have to be manually processed by administrators on translatewiki before they are imported into the system for translators to see.

vivian-rook opened https://github.com/toolforge/paws/pull/462

updates:

• cloud-flat-1-ipv4only (eqiad1) 172.16.8.0/21 https://netbox.wikimedia.org/ipam/prefixes/1076/
• cloud-flat-1-dualstack-ipv4 (eqiad1) 172.16.16.0/21 https://netbox.wikimedia.org/ipam/prefixes/1103/
• cloud-flat-codfw1dev-ipv4only 172.16.130.0/24 https://netbox.wikimedia.org/ipam/prefixes/1101/

In T362379#10343726, @Mvolz wrote:

In T362379#10343714, @Robertsky wrote:

FYI, it seems that straitstimes.com may be blocked now as well.

Yup. Very clear block starting Nov 5th 2024 visible: https://logstash.wikimedia.org/app/dashboards#/view/5eaf4e40-f6b6-11eb-85b7-9d1831ce7631?_g=(filters%3A!()%2CrefreshInterval%3A(pause%3A!t%2Cvalue%3A0)%2Ctime%3A(from%3Anow-3M%2Cto%3Anow))

We're not sending them more than 30 requests/day so :/ The day they blocked us, only 3 requests!

Change #1093882 merged by jenkins-bot:

[mediawiki/extensions/ReportIncident@master] dialog: Disable instrumentation by default

https://gerrit.wikimedia.org/r/1093882

Change #1093887 merged by jenkins-bot:

[mediawiki/extensions/CheckUser@master] selenium: Replace Node.js Assert library with WebdriverIO Expect library

https://gerrit.wikimedia.org/r/1093887

[Please use the feature form linked at the top to create feature requests - thanks!]

In T378451#10307350, @Yann wrote:

May I know how long this will take?

Until someone finds time to volunteer to do this. No need to remind about weeks.

In T362379#10343714, @Robertsky wrote:

FYI, it seems that straitstimes.com may be blocked now as well.

Also, we might want to have a broader conversation since we have other initiatives improving the nodejs ecosystem, see T357950: Remove servicerunner dependency for cxserver

Hi @Seddon - I’m wrapping up my review and haven’t found any blockers so far.

I am removing RESTBase Sunsetting as this is not needed for it's compeltion. Proton has been migrated already.

I am removing RESTBase Sunsetting as this is not needed for its completion. Please, re-add it if needed.

In T95100#10343681, @Nikki wrote:

This is really annoying, how do I turn it off?

You probably mean the change in T377663: Support autocompletion in CodeEditor. CodeMirror 6 isn’t available anywhere other than mediawiki.org yet and I don't think autocompletion is there at all.

FYI, it seems that straitstimes.com may be blocked now as well.

At this point, VE is already using Parsoid directly without the REST layer as per T320529: Configure VE backend to use Parsoid directly, instead of calling RESTbase. The remainder tickets here are not needed for the epic completion so I'm closing it. Please let me know in case I'm missing something.

@CCiufo-WMF If no one is planning to continue working on this task, I’d be happy to volunteer and take it forward.