User Details
- User Since
- Jun 29 2021, 9:56 AM (271 w, 4 d)
- Availability
- Available
- IRC Nick
- btullis
- LDAP User
- Btullis
- MediaWiki User
- BTullis (WMF) [ Global Accounts ]
Yesterday
Here is the output when running the script on the two WMCS clusters.
I have written and deployed the check script: /usr/local/sbin/verify-cephx-keys
It is deployed on these hosts:
Thu, Sep 10
I think that this is is another one of those times when the disk hasn't actually failed, but it was disconnected by the RAID controller, temporarily.
This one keeps dropping disks. I've added the parent task where I'm doing a larger investigation into what seems like a batch of servers where this keeps happening.
Wed, Sep 9
Tue, Sep 8
The workers are in their production role, puppet runs cleanly, and they have been uncordoned.
root@deploy1003:~# kubectl get nodes NAME STATUS ROLES AGE VERSION dse-k8s-ctrl2001.codfw.wmnet Ready control-plane 358d v1.31.14 dse-k8s-ctrl2002.codfw.wmnet Ready control-plane 358d v1.31.14 dse-k8s-wdqs-test2001.codfw.wmnet Ready <none> 99d v1.31.14 dse-k8s-wdqs2001.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2002.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2003.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2004.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-worker2001.codfw.wmnet Ready <none> 358d v1.31.14 dse-k8s-worker2002.codfw.wmnet Ready <none> 358d v1.31.14 dse-k8s-worker2003.codfw.wmnet Ready <none> 333d v1.31.14 dse-k8s-worker2004.codfw.wmnet Ready,SchedulingDisabled <none> 20m v1.31.14 dse-k8s-worker2005.codfw.wmnet Ready,SchedulingDisabled <none> 14m v1.31.14 root@deploy1003:~# kubectl uncordon dse-k8s-worker2004.codfw.wmnet dse-k8s-worker2005.codfw.wmnet node/dse-k8s-worker2004.codfw.wmnet uncordoned node/dse-k8s-worker2005.codfw.wmnet uncordoned root@deploy1003:~# kubectl get nodes NAME STATUS ROLES AGE VERSION dse-k8s-ctrl2001.codfw.wmnet Ready control-plane 358d v1.31.14 dse-k8s-ctrl2002.codfw.wmnet Ready control-plane 358d v1.31.14 dse-k8s-wdqs-test2001.codfw.wmnet Ready <none> 99d v1.31.14 dse-k8s-wdqs2001.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2002.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2003.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-wdqs2004.codfw.wmnet Ready <none> 82d v1.31.14 dse-k8s-worker2001.codfw.wmnet Ready <none> 358d v1.31.14 dse-k8s-worker2002.codfw.wmnet Ready <none> 358d v1.31.14 dse-k8s-worker2003.codfw.wmnet Ready <none> 333d v1.31.14 dse-k8s-worker2004.codfw.wmnet Ready <none> 26m v1.31.14 dse-k8s-worker2005.codfw.wmnet Ready <none> 20m v1.31.14 root@deploy1003:~#
Added the nodes to conftool-data and pooled them.
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw' get|sort
{"dse-k8s-wdqs2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2002.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2003.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2004.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs-test2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2002.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2003.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2004.codfw.wmnet": {"weight": 0, "pooled": "inactive"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2005.codfw.wmnet": {"weight": 0, "pooled": "inactive"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2004.codfw.wmnet' set/weight=10
codfw/dse-k8s/kubesvc/dse-k8s-worker2004.codfw.wmnet: weight changed 0 => 10
WARNING:conftool.announce:conftool action : set/weight=10; selector: service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2004.codfw.wmnet
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2005.codfw.wmnet' set/weight=10
codfw/dse-k8s/kubesvc/dse-k8s-worker2005.codfw.wmnet: weight changed 0 => 10
WARNING:conftool.announce:conftool action : set/weight=10; selector: service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2005.codfw.wmnet
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2004.codfw.wmnet' set/pooled=yes
codfw/dse-k8s/kubesvc/dse-k8s-worker2004.codfw.wmnet: pooled changed inactive => yes
WARNING:conftool.announce:conftool action : set/pooled=yes; selector: service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2004.codfw.wmnet
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2005.codfw.wmnet' set/pooled=yes
codfw/dse-k8s/kubesvc/dse-k8s-worker2005.codfw.wmnet: pooled changed inactive => yes
WARNING:conftool.announce:conftool action : set/pooled=yes; selector: service=kubesvc,cluster=dse-k8s,dc=codfw,name=dse-k8s-worker2005.codfw.wmnet
btullis@puppetserver1001:~$ sudo confctl select 'service=kubesvc,cluster=dse-k8s,dc=codfw' get|sort
{"dse-k8s-wdqs2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2002.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2003.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs2004.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-wdqs-test2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2001.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2002.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2003.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2004.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
{"dse-k8s-worker2005.codfw.wmnet": {"weight": 10, "pooled": "yes"}, "tags": "dc=codfw,cluster=dse-k8s,service=kubesvc"}
btullis@puppetserver1001:~$I restarted all radosgw daemons and everything seems OK.
Disabling standby replay.
btullis@cephosd2001:~$ sudo ceph fs ls name: dpe, metadata pool: cephfs.dpe.meta, data pools: [cephfs.dpe.data-ssd ]
I have restarted all OSD daemons by running the following an all three hosts, several minutes apart.
sudo systemctl restart ceph-osd.target
We can see the new versions being reported here: https://grafana-rw.wikimedia.org/goto/s4mw5r?orgId=default
Restarting the mgr daemons on each host.
Going for it now.
Since ours is a co-located installation and all daemons are on the same hosts, it is not possible to defer the installation of the packages. When I try to install the ceph-mon package, all of the other relevant daemons are upgraded, too.
The procedure set out here https://docs.ceph.com/en/latest/releases/squid/#upgrading-non-cephadm-clusters is broadly as follows:
A few weeks later, after our upgrade to bookworm on all of these an-worker hosts, I run the command again to see how many hosts have fewer than 12 hadoop-* data volumes.
btullis@cumin1003:~$ sudo cumin A:hadoop-worker 'blkid |grep -c hadoop-' 94 hosts will be targeted: an-worker[1142-1147,1149-1236].eqiad.wmnet OK to proceed on 94 hosts? Enter the number of affected hosts to confirm or "q" to quit: 94 ===== NODE GROUP ===== (1) an-worker1200.eqiad.wmnet ----- OUTPUT for command #1: 'blkid |grep -c hadoop-' ----- 10 ===== NODE GROUP ===== (4) an-worker[1144,1198-1199,1204].eqiad.wmnet ----- OUTPUT for command #1: 'blkid |grep -c hadoop-' ----- 11 ===== NODE GROUP ===== (89) an-worker[1142-1143,1145-1147,1149-1197,1201-1203,1205-1236].eqiad.wmnet ----- OUTPUT for command #1: 'blkid |grep -c hadoop-' ----- 12 ================
5 of the 94 hadoop workers are currently showing as having dropped at least one disk.
Mon, Sep 7
Here is the homer diff, after enabling BGP for the two hosts.
btullis@cumin1003:~$ sudo homer lsw1-a?-codfw* diff INFO:homer.devices:Initialized 129 devices INFO:homer:Generating diff for query lsw1-a?-codfw* INFO:homer:Gathering global Netbox data INFO:homer.devices:Matched 7 device(s) for query 'lsw1-a?-codfw*' INFO:homer:Generating configuration for lsw1-a2-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Running commit check on lsw1-a2-codfw.mgmt.codfw.wmnet INFO:homer:Generating configuration for lsw1-a3-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Empty diff for lsw1-a3-codfw.mgmt.codfw.wmnet, skipping device. INFO:homer:Generating configuration for lsw1-a4-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Empty diff for lsw1-a4-codfw.mgmt.codfw.wmnet, skipping device. INFO:homer:Generating configuration for lsw1-a5-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Empty diff for lsw1-a5-codfw.mgmt.codfw.wmnet, skipping device. INFO:homer:Generating configuration for lsw1-a6-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Empty diff for lsw1-a6-codfw.mgmt.codfw.wmnet, skipping device. INFO:homer:Generating configuration for lsw1-a7-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Running commit check on lsw1-a7-codfw.mgmt.codfw.wmnet INFO:homer:Generating configuration for lsw1-a8-codfw.mgmt.codfw.wmnet INFO:homer.transports.junos:Empty diff for lsw1-a8-codfw.mgmt.codfw.wmnet, skipping device. Changes for 1 devices: ['lsw1-a2-codfw.mgmt.codfw.wmnet']
I have created T437233: ceph: Fix the CephX key guard so that Puppet can correctly update the key material to fix the puppet management of CephX key data.
I don't think that the systemd unit name change is going to bite us, after all.
I still see the existing names of systemd units in https://github.com/ceph/ceph/tree/v19.2.0/systemd so I think that this actually affects cephadm clusters. Maybe it's a documentation bug.
I think that I'm going to decline this one, having looked at it again in the context of T428445: Upgrade Data Platform ceph clusters to version 19 - squid.
Thanks, yes I agree that this was a bit wooly and vague. How does this version of the SeaTunnel description sound, instead?
This is now OK.
btullis@cephosd1001:~$ sudo ceph health detail HEALTH_OK
I see this from the journal entry for the ceph-osd@80.service until on cephosd1005.
Sep 07 11:03:49 cephosd1005 ceph-osd[4055]: 2026-09-07T11:03:49.206+0000 7fc468dd26c0 -1 log_channel(cluster) log [ERR] : 19.3b0 repair 1 errors, 1 fixed
Not investigating any further, so I'll resolve this ticket.
I have just executed this command.
btullis@cephosd1001:~$ sudo ceph pg repair 19.3b0 instructing pg 19.3b0 on osd.80 to repair
Oh, this is also interesting. From here: https://docs.ceph.com/en/latest/releases/squid/#upgrading-non-cephadm-clusters
I'm reviewing the notable changes and critical upgrade steps for this upgrade.
I have updated preseed.yaml and site.pp for these new nodes, so I think that I'm done for now.
Sun, Sep 6
Fri, Sep 4
Assigning to @JAllemandou for guidance at this stage.
Thu, Sep 3
I think that this is all done now. I have removed the development schema and the eventstream config for it.
As I understand it (from T435952 and T436758) , the back-end service hosting these files for the period of the experiment will be: analytics.wikimedia.org
We now have data in the hive table.
spark-sql (default)> select count(*) from event.webrequest_dumps_v1 where year=2026 and month=9 and day=3; count(1) 149722 Time taken: 12.268 seconds, Fetched 1 row(s)
I checked on https://stream-internal.wikimedia.org/v2/ui/#/?streams=webrequest.dumps.v1 and we have live data in eventstreams from the dumps servers.
Also confirmed that we have a continuous dataset in logstash.
Wed, Sep 2
The new eventstreams are being ingested by gobblin.
https://grafana-rw.wikimedia.org/goto/shfcn5?orgId=default
Canary testing with Wikimedia Debug extension looks good to me.
I have scheduled a backport deployment of the eventstreams patch for this afternoon.
There are some instructions on how to publish to analytics.wikimedia.org here: https://wikitech.wikimedia.org/wiki/Data_Platform/Web_publication
Fri, Aug 21
I believe that @bking will be able to run the upgrades next week.
Boldly resolving.
Pupet is running cleanly. Closing.



