After running it for the second time this bug appears to be gone!
So a temporary fix would be to just repeat the upgrade.
After running it for the second time this bug appears to be gone!
So a temporary fix would be to just repeat the upgrade.