-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
user_parter removes other users from room when deactivation endpoint is called #16582
Comments
These lines should only be logged if userB and userC are pending deactivation: https://github.com/matrix-org/synapse/blob/v1.94.0/synapse/handlers/deactivate_account.py#L237-L240 Can you confirm (or refute) that these users have been deactivated? |
These users were not deactivated through the admin API. From the admin API I can see the following information: {
"name": "@userB:myhomeserver",
"admin": false,
"deactivated": false,
"locked": false,
"shadow_banned": false,
"creation_ts": 1693854141,
"appservice_id": null,
"consent_server_notice_sent": null,
"consent_version": null,
"consent_ts": null,
"user_type": null,
"is_guest": false,
"displayname": "userB",
"avatar_url": null,
"threepids": [],
"external_ids": [
{
"auth_provider": "oidc-keycloak",
"external_id": "..."
}
],
"erased": false,
"last_seen_ts": 1698432079706
} {
"name": "@userC:myhomeserver",
"admin": false,
"deactivated": false,
"locked": false,
"shadow_banned": false,
"creation_ts": 1698440166,
"appservice_id": null,
"consent_server_notice_sent": null,
"consent_version": null,
"consent_ts": null,
"user_type": null,
"is_guest": false,
"displayname": "userC",
"avatar_url": null,
"threepids": [],
"external_ids": [
{
"auth_provider": "oidc-keycloak",
"external_id": "..."
}
],
"erased": false,
"last_seen_ts": 1698447042385
} |
Odd. Both show up as synapse/synapse/handlers/deactivate_account.py Lines 139 to 141 in 9407d5b
|
Unfortunately I did not get a response from the initially affected users, but the same issue occured again today. Two unrelated users got parted from all rooms, the admin API reports them as not deactivated.
However, the server has no enabled federation and there are no remote users in that room. |
Description
Whenever I call the deactivate (+erase) endpoint on synapse (this case for userA) it kept removing another user (userB) from all rooms.
Today this happened for a second user (userC). The notable difference here is that userB had left one of the rooms on their own. C hasn't so far.
Steps to reproduce
Homeserver
Selfhostes
Synapse Version
1.94.0
Installation Method
Docker (matrixdotorg/synapse)
Database
single postgres server, no restore from backup
Workers
Single process
Platform
Debian 11 with docker
Configuration
Presence and retention are enabled in the affected public rooms.
The public rooms have a 48h retention policy for about 1.5 years.
The homeserver does not federate.
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: