[04:52:33] andrewbogott: hi! The user data is kept under, I think, /srv/paws/project... Follow the data it's pretty large [04:53:01] For the magnum ticket that seemed to get fixed when fcos was updated [04:53:37] The patch that we were applying locally didn't seem to work so it can, probably, be removed. [08:42:37] dhinus: thanks for your quick review yesterday on https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/163 I would like to get it merged this morning [08:42:59] but because the `move` blocks, will need separate merges for eqiad1/codfw1dev [08:57:44] arturo: sounds good, I'll have another look in a moment [09:34:37] arturo: can you run a "tofu plan" on codfw to check it's a no-op? the last tofu plan I see in the MR is old [09:34:52] then I'm fine with the two separate merges [09:49:07] sorry, I was in a meeting [09:49:16] I'll create a MR only for codfw1dev [09:50:14] ok! [13:12:24] FYI I gave chuckonwu 'owner' permissions on cloud/ repos on gitlab [13:12:55] let me know if you would rather have a more granular assignment [13:14:02] arturo: I think that's fine [13:59:02] thanks [14:14:11] quick +1 here ? https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/167 [14:17:55] sorry about all the emails, trying to reduce the volume for the next round of reboots [14:18:29] arturo: +1d [14:18:39] thanks! [15:29:37] dhinus: have a minute to help me with a db schema issue? Trove seems to have a mistake in the db upgrade script and I'm having a hard time understanding the failure [15:29:55] you can see it if you log into cloudcontrol1005.eqiad.wmnet and run 'sudo trove-manage db_sync' [15:30:22] the migrations are in /usr/lib/python3/dist-packages/trove/db/sqlalchemy/migrations [15:33:08] :-( [15:36:03] I have a work around prepared but somehow the failure is different in eqiad1 than it was in codfw1dev [15:39:36] * arturo offline [15:40:26] andrewbogott: looking [15:41:46] AttributeError: Could not locate column in row for column 'values' <- not helpful [15:43:47] I wonder if it's a version mismatch problem [15:44:11] I found https://stackoverflow.com/a/72921642/1765344 [15:45:00] possible. Same version in codfw1dev though and I got it to work there (although not without a hack) [15:45:55] I would be fine with just applying the update by hand, it's not very many changes. [15:45:58] haven't tried that yet though [15:49:56] how would you apply it by hand? looking into the py migration file and manually translating to SQL commands? [15:50:49] it might work but it's a bit tedious, you could then update whichever table is used to keep track of applied migrations [15:51:44] yeah, it's not straightforward. [15:51:47] I would first try playing with installing different sqlalchemy versions (with pip or some other way) [15:51:52] Can you even tell from the error message which step is failing? [15:51:55] and see if there's one where the script works [15:52:29] ok. Looks like we used to be running 1.4, let's see if I can get that installed [15:53:09] I'm not seeing which step is failing, no [15:54:16] reverting to 1.4.46+ds1-1 seems to have worked! [15:54:24] well, I think... [15:54:33] does db_sync look good to you now? It's so verbose... [15:54:55] I wish a second run would just produce no output... [15:55:27] * andrewbogott restarts the cookbook [15:58:15] should I wait for you to run the cookbook, or can I run db_sync now? [16:00:47] the host is rebooting now :) so at least the cookbook thinks we're unstuck. [16:00:55] Thanks! We'll see if trove still works after the upgrade, I guess [16:01:48] nice! I will log off soon, but let me know if it's still broken and I can look later/tomorrow