Using `mock -r epel-6-x86_64 --shell` on VM in AWS, I ended up with: ``` .... Error: Failed to download metadata for repo 'epel': repomd.xml parser error: Parse error at line: 85 (expected '>' ) WARNING: Dnf command failed, retrying, attempt #2, sleeping 10s ``` That was because the preferred mirror contained repomd.xml file which was missing the terminating '>\n' character sequence: $ curl --silent https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/6/x86_64/repodata/repomd.xml | tail -n2 </data> </repomd$ I'd expect that dnf continues to next mirror from mirrorlist, but it doesn't. $ rpm -q dnf libsolv hawkey rpm librepo dnf-4.2.18-1.fc31.noarch libsolv-0.7.11-1.fc31.x86_64 package hawkey is not installed rpm-4.15.1-1.fc31.x86_64 librepo-1.11.1-1.fc31.x86_64
A very similar problem now exists for everyone in AWS probably, meh. The server dl.fedoraproject.org is "mirrored" through (from AWS instances the closest) mirror: https://d2lzkl7pfhq30w.cloudfront.net/ which has the content either cached in s3 directly, or it forwards the non-cached requests directly to dl.fedoraproject.org - which is dead ATM: https://pagure.io/fedora-infrastructure/issue/9051 The problem seems to be that we try to download the repomd.xml from the closest mirror, which points to AWS mirror, which is _down_ because dl.fedoraproject.org is down. The mirroring system would otherwise work pretty fine, it's a pity we don't try it.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Seems still like something we should at least discuss a bit. The situation is relatively rare, but if that happened again - e.g. Copr build system would stop building the affected chroot for several hours or days.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.