-
Notifications
You must be signed in to change notification settings - Fork 427
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
_get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. #561
Comments
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior The Azure mirrors have allowed list of arches
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior The Azure mirrors have allowed list of arches
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 1, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 4, 2022
- No source of entropy in _get_nearest_mirrors_by_network_data() - _get_nearest_mirrors_by_network_data() fails to exclude near-by private mirrors for extra options. - Exclude the private mirrors from the mirrors list in the case of fallback behavior - The Azure mirrors have allowed list of arches - Decrease level of logging messages in some cases - Cache subnets of Azure/AWS cloud
soksanichenko
pushed a commit
that referenced
this issue
Jul 7, 2022
soksanichenko
pushed a commit
that referenced
this issue
Jul 7, 2022
The patch is deployed to production |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/AlmaLinux/mirrors/blob/mirrors_service/src/backend/api/handlers.py#L105-L117
When a client matches against the network data service cone of a mirror, the list offered to them is appended up to LENGTH_CLOUD_MIRROR_LIST (5) with other nearby mirrors.
This list of additional mirrors can include private mirrors if the private mirror accidentally included geo data in their configuration.
This suitable_mirrors.extend also fails to check the health of these additional mirrors, meaning that the additional mirrors are not verified to be ok and may be outdated or flapping.
Failure mode is that if a mirror with a specified network data match for clients goes down, when the clients slide down the list to subsequent mirrors, this list of additional mirrors is not filtered for private mirrors or only healthy mirrors.
The text was updated successfully, but these errors were encountered: