You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am hot sure, but I believe there may be an edge case where a user record may not be properly migrated. tokenserver::handlers::update_user(..) only migrates the user via db.post_user(..) if the req.auth_data.client_state (from the auth token) does not match the req.user.client_state (from the stored user record). (The later generation check does not alter the node_id.)
I have no idea how the user could end up in this state, and it presumes that the auth token has not changed, but we should check the user's previous node_id to see if it matches the spanner_node_id and force an update if it does not.
We have some users still reporting that they’re on AWS nodes. We should force all users to go to the Spanner node.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: