Mentioned in SAL (#wikimedia-operations) [2019-10-17T09:57:28Z] <godog> swift codfw-prod: more weight to ms-be205[1-6] - T233638

This topic was discussed in details and the current undestanding is given below:

Testing on https://test.wikipedia.org that:

Change 543137 merged by Arturo Borrero Gonzalez:
[operations/puppet@production] toolforge: k8s: adjust ports in the ingress setup

Change 542117 merged by jenkins-bot:
[mediawiki/extensions/Popups@master] Split user preferences for Page and Reference previews

Change 542140 merged by jenkins-bot:
[mediawiki/extensions/Popups@master] Refactor PopupsHooks for easier removal and/or expansion

Thanks, @ovasileva! Let's go with "Previews" for now. This is really just the Special:Version page and nothing else. We can change it again any time if needed.

inherits.js:5 Uncaught TypeError: Super expression must either be null or a function

Change 503405 merged by jenkins-bot:
[mediawiki/extensions/Translate@master] Remove hr element from page translation header

I received about 1000 mails in two days, glad that I set up a filter...

Mentioned in SAL (#wikimedia-operations) [2019-10-17T09:39:38Z] <godog> swift eqiad-prod: add weight to ms-be105[1-6] - T232367

db1129 and db1117 are good to go.

Mentioned in SAL (#wikimedia-operations) [2019-10-17T09:37:54Z] <marostegui@cumin1001> dbctl commit (dc=all): 'Depool db1129 for PDU work, give some traffic to db1090:3312 meanwhile T22meanwhile T227133', diff saved to https://phabricator.wikimedia.org/P9374 and previous config saved to /var/cache/conftool/dbconfig/20191017-093753-marostegui.json

In T234051#5582768, @Jrogers-WMF wrote:

That said, could you tell me what kind of review there would be for a policy against undeleting by patrollers? If violations of that policy would be noticed fairly quickly, I think that would address the concern because they'd be given the right only for helping to clean up content, but if an undeletion might go unnoticed for a long while, I'd be more hesitant.

postponed till after wikigap meeting

Mentioned in SAL (#wikimedia-operations) [2019-10-17T09:26:32Z] <marostegui> Stop MySQL on db1117 this will generate some haproxy alerts - T227133

Which namespace(s) and/or categories the Help panel search should handle (0 is mandatory)

Have you ever used 7G Hosting, If yes how was your experience can I buy a package from them to host my project.

Fine by me, thanks!

Patch is up demonstrating what we tried. You'll notice CSR works perfectly and that in the Mediawiki RL environment it throws an error like this:

inherits.js:5 Uncaught TypeError: Super expression must either be null or a function
    at E (inherits.js:5)
    at TaintedIcon.vue:10
    at Module.cd49 (TaintedIcon.vue:10)
    at n (bootstrap:19)
    at Module.fd46 (tainted-ref.init.js?09d4a:26)
    at n (bootstrap:19)
    at bootstrap:83
    at tainted-ref.init.js?09d4a:1
E @ inherits.js:5
(anonymous) @ TaintedIcon.vue:10
cd49 @ TaintedIcon.vue:10
n @ bootstrap:19
fd46 @ tainted-ref.init.js?09d4a:26
n @ bootstrap:19
(anonymous) @ bootstrap:83
(anonymous) @ tainted-ref.init.js?09d4a:1

@Tim_WMDE Not to change banner behaviour (yet) is correct. But I'am stumbling (and maybe not understanding correctly) about to track the viewports of wikipedia.de visits in general (and unrelated to a actual display of a banner). To track if a banner size issue would have occured and at which viewport width this happens (as Till writes, a "potential banner size issue") the actual banner (height) would needed to be taken into account (calculating the difference of max. banner height and actual banner height). Therefor I wonder what you mean by viewport tracking even if no banners are present.

Change 543802 had a related patch set uploaded (by Tarrow; owner: Tarrow):
[mediawiki/extensions/Wikibase@master] DNM: try to need only one RL module

Change 540871 merged by Elukey:
[eventlogging@master] Move codebase to Python3

Thanks for the answer.

I checked in the Wikidata team what the status was and we hope to have some additional code for review soon (hopefully today). Sorry about the delay.

Change 539065 merged by Arturo Borrero Gonzalez:
[operations/puppet@production] openstack: drop jessie code

Change 543800 had a related patch set uploaded (by Thiemo Kreuz (WMDE); owner: Thiemo Kreuz (WMDE)):
[mediawiki/extensions/Popups@master] Remove obsolete mediaWiki and jQuery aliases

Change 543799 merged by Muehlenhoff:
[operations/dns@master] Remove DNS entries for labpuppetmaster

In T233092#5564494, @daniel wrote:

Has the new version of quibble been deployed everywhere?
Should CI on the api-testing repo now be using the hardcoded secret?

Change 543183 merged by Ayounsi:
[operations/homer/public@master] Remove zookeeper terms from the Analytics filters

This got resolved with the cergen build for buster.

What's the status of this? It seems like this migration is in some limbo state :)

Change 543799 had a related patch set uploaded (by Muehlenhoff; owner: Muehlenhoff):
[operations/dns@master] Remove DNS entries for labpuppetmaster

cool thanks! I will work on the operation steps soon for you to review.

Re-opening since we have a new sub-task.

Oops, wrong task.

In T212258#5582604, @Isaac wrote:

@elukey I'm having trouble ssh-ing into an-tool1006.eqiad.wmnet (ssh isaacj@an-tool1006.eqiad.wmnet) where it is not letting me on the server (doesn't accept my password) -- is it possible that I need to be added as a user to the machine or is it an issue on my end? thanks!

Re-opening since we have a new sub-task.

Change 543798 merged by Elukey:
[operations/puppet@production] role::analytics_test_cluster::client: allow ssh access to analytics users

Given that neither of the newly filed issues originated in this story, would it be fair to call this done?

Change 543715 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Change 2nd monthly convert email to use original_currency.

Hey, sorry for the clumsy phrasing. You're both correct in your interpretation.

Change 543797 merged by Muehlenhoff:
[operations/puppet@production] labpuppetmaster: Remove remaining puppet references

There have been no objections in more than a month, so I think this is good to go. I'll add it to the European mid-day SWAT.

Change 543798 had a related patch set uploaded (by Elukey; owner: Elukey):
[operations/puppet@production] role::analytics_test_cluster::client: allow ssh access to analytics users

Here is my feedback after some testing sessions on the banner:

Change 543797 had a related patch set uploaded (by Muehlenhoff; owner: Muehlenhoff):
[operations/puppet@production] labpuppetmaster: Remove remaining puppet references

Change 543796 had a related patch set uploaded (by Jon Harald Søby; owner: Jon Harald Søby):
[operations/mediawiki-config@master] Allow sysops to add transwiki on nnwiki, and add import sources

Images from local testing,

Thanks for the update!

cookbooks.sre.hosts.decommission executed by jmm@cumin1001 for hosts: labpuppetmaster1002.wikimedia.org

• labpuppetmaster1002.wikimedia.org (PASS)
  • Downtimed host on Icinga
  • Downtimed management interface on Icinga
  • Wiped bootloaders
  • Powered off
  • Set Netbox status to Decommissioning
  • Removed from DebMonitor
  • Removed from Puppet master and PuppetDB

cookbooks.sre.hosts.decommission executed by jmm@cumin1001 for hosts: labpuppetmaster1001.wikimedia.org

• labpuppetmaster1001.wikimedia.org (PASS)
  • Downtimed host on Icinga
  • Downtimed management interface on Icinga
  • Wiped bootloaders
  • Powered off
  • Set Netbox status to Decommissioning
  • Removed from DebMonitor
  • Removed from Puppet master and PuppetDB

This function was moved around multiple times now. I'm not sure since when $.escapeRE existed, but I remember when it stopped working without a hint I was able to notice in time. All user scripts I wrote broke, leaving all my users puzzled. Just a few months later the same scripts broke again because the function stopped being available without requesting it first. That was the point I got sick of running after a single line (!) of code and copy pasted it into my code.

The difference is the following .... if you try to put in the wiki twice the same property: