Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a different key ID for each complement server #486

Merged
merged 1 commit into from
Oct 6, 2022

Conversation

squahtx
Copy link
Contributor

@squahtx squahtx commented Sep 30, 2022

Some tests may choose to re-use the same homeserver deployment across
multiple test cases, each spinning up different complement servers.
However, when a complement server happens to have the same hostname and
port as a previous one, the homeserver under test may retain cached keys
for the old complement server and reject events from the new one.

Give each complement server a unique key ID to stop that from happening.


Thanks to @erikjohnston for suggesting the fix.

Fixes matrix-org/synapse#13975.

Some tests may choose to re-use the same homeserver deployment across
multiple test cases, each spinning up different complement servers.
However, when a complement server happens to have the same hostname and
port as a previous one, the homeserver under test may retain cached keys
for the old complement server and reject events from the new one.

Give each complement server a unique key ID to stop that from happening.
@squahtx squahtx requested review from a team and kegsay as code owners September 30, 2022 14:14
@squahtx squahtx merged commit f4eebb1 into main Oct 6, 2022
@squahtx squahtx deleted the squah/use_unique_keyid_for_complement_server branch October 6, 2022 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Complement flake(?) TestPartialStateJoin/* due to complement hostname:port re-use
3 participants