🇮🇹Italy mrcelli
@cilefen there are custom modules but nothing related to the issue.
This bug started happening after upgrading from Drupal 9 to Drupal 10.
The custom modules/code are the same, thus irrelevant imho.
🇮🇹Italy mrcelli
I got the error after upgrading to drupal 10.
In my case it is related to a second database used by other containers.
None of the above suggestions worked.
I deleted the tables which were mentioned in the message as missing the primary keys but they still appear in the message!
I finally have disconnected the entire database from the settings.php but the error is still there.
So, I think the issue here is that drupal core status page does NOT UPDATE that error or whatever scans through it does run only once and gets stuck.
Anyone have any ideas?