Upgrading to Drupal 9.3.x changes users table and locks users out of the site

Having read through this issue, it looks like the following actions are needed to resolve:

1. Test and review MR 79 to ensure sqlsrv can cope with schema changes that convert columns to serial.
2. Implement an update function to ensure the user uid column is converted to serial as per user_update_9301. This update function should ensure it only attempts to do work if the column is not already an appropriate identity column in the database (i.e. if the site admin has already fixed the schema manually to work round the problem while awaiting the fix from this issue).

Is this correct?

@pstewart

I think number 2 will fix the problem with the user table. I could not find any way to manually fix the schema to get around the problem.

Hi:
I ran to this same issue when upgrading a production site from 9.2 to 9.5.
After the database update there was not posible to create users so i fixed the schema manually to work around the problem but now i had a error on the site state report:

No coinciden las definiciones de entidad y/o campo
Se detectaron los siguientes cambios en las definiciones de tipo de entidad y de campo.
Usuario
El campo ID de Usuario necesita ser actualizado.

Any idea how to solve it?

Hi:
I ran to this problem when upgrading a site from drupal 9.2 to 9.5, as the script does not work i fixed the schema manually to work around the problem but im getting an error on the report status..

userid definition error.png

Any idea what to solve this?

Regards.

The translation of the above comment:

Entity and/or field definitions do not match The following changes were detected in the entity type and field definitions. User The User ID field needs to be updated.

Updating target branch

pstewart → credited glassb → .

pstewart → credited JerryACSA → .

Noting that most of the discussion has been happening on 🐛 SQL Server Identity error when updating to Drupal 10.1.0 RTBC , which includes successful testing of MR87. The merge request will be completed on this issue and once this issue has been closed as fixed the other issue will be closed as duplicate.

pstewart → changed the visibility of the branch 3263493-upgrading-to-drupal to hidden.

Should this now be closed as Fixed?

I'm planning to mark all the issues resolved in 4.4.x as fixed when we do the stable release, which will hopefully be the same as rc1 if no problems arise.

Automatically closed - issue fixed for 2 weeks with no activity.