To wrap this up, I tried the upgrade again a few days later, and the issue magically vanished. This must have been something very strange that has happened during the borked upgrade, I suspect some ruby issue since the ruby upgrade didn’t go quite well in the first instance.
Sorry for the noise.
1 Like