Dec 07 06:35:44 one.example.com dnf-automatic[3635738]: Errors during downloading metadata for repository 'AppStream': Dec 07 06:35:44 one.example.com dnf-automatic[3635738]: - Status code: 404 for http://centos.les.net/8-stream/AppStream/x86_64/os/repodata/repomd.xml.asc (IP: 199.87.157.230) Dec 07 06:35:44 one.example.com dnf-automatic[3635738]: Error: Failed to download metadata for repo 'AppStream': GPG verification is enabled, but GPG signature is not available. This may be an error or the repository does not support GPG verification: Status code: 404 for http://centos.les.net/8-stream/AppStream/x86_64/os/repodata/repomd.xml.asc (IP: 199.87.157.230)
or
Dec 07 06:27:33 two.example.com dnf-automatic[233137]: Errors during downloading metadata for repository 'AppStream': Dec 07 06:27:33 two.example.com dnf-automatic[233137]: - Status code: 404 for http://pkg.adfinis.com/centos/8-stream/AppStream/x86_64/os/repodata/repomd.xml.asc (IP: 2001:618:1:129::165) Dec 07 06:27:33 two.example.com dnf-automatic[233137]: Error: Failed to download metadata for repo 'AppStream': GPG verification is enabled, but GPG signature is not available. This may be an error or the repository does not support GPG verification: Status code: 404 for http://pkg.adfinis.com/centos/8-stream/AppStream/x86_64/os/repodata/repomd.xml.asc (IP: 2001:618:1:129::165)
while I'll keep this request open here, it's meant for Stream team so not on this tracker normally. I've assigned @hughesjr on it (external to infra and releng team)
infra and releng
Metadata Update from @arrfab: - Issue assigned to hughesjr - Issue tagged with: centos-build-pipeline, centos-stream
and it's true that they probably pushed again a tree without repodata being signed, as it's missing everywhere : http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/repodata/
Where should one usually report Stream infra issues?
per wiki instructions (https://wiki.centos.org/ReportBugs) it's stream so should be on https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&version=CentOS%20Stream but let's keep it here and you can then ping the assignee (probably on irc instead) to have a look
better, let me assign the official Stream PO
Metadata Update from @arrfab: - Issue assigned to amoloney (was: hughesjr)
A BZ ticket requires a component - at least the component field has a red start and thus is imho mandatory. There is no component infra nor mirrors nor ...
For issues in packages it is clear to me, but for general infra issues? And sorry to abuse the ticket for chatting.
Hi Marcel,
Ive asked someone on the CentOS Stream team to look into it so we will work resolving it. Its fine to have this ticket open for this issue too. Thanks for opening it and bringing it to our attention.
Aoife
On Tue, Dec 7, 2021 at 3:37 PM Marcel Haerry pagure@pagure.io wrote:
maha added a new comment to an issue you are following: `` A BZ ticket requires a component - at least the component field has a red start and thus is imho mandatory. There is no component infra nor mirrors nor ... For issues in packages it is clear to me, but for general infra issues? And sorry to abuse the ticket for chatting. `` To reply, visit the link below or just reply to this email https://pagure.io/centos-infra/issue/550
maha added a new comment to an issue you are following: `` A BZ ticket requires a component - at least the component field has a red start and thus is imho mandatory. There is no component infra nor mirrors nor ...
For issues in packages it is clear to me, but for general infra issues? And sorry to abuse the ticket for chatting. ``
To reply, visit the link below or just reply to this email https://pagure.io/centos-infra/issue/550
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA https://www.redhat.com
Communications House
Cork Road
Waterford https://www.redhat.com
JFI: this is a recurring issue: https://pagure.io/centos-infra/issue/510
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
JFI: repomd.xml.asc is missed again ...
Metadata Update from @arrfab: - Issue status updated to: Open (was: Closed)
Metadata Update from @arrfab: - Issue marked as depending on: #510
reopened and waiting for someone from CentOS Stream to pick it up
Good morning, this issue was resolved yesterday and some additional checks have been added so it hopefully shouldn't happen again.
Please reopen this ticket if it does and we will recheck.
Thanks for your patience! Aoife
Closing, per @amoloney 's answer
JFI: repomd.xml.asc is missed again ... (c8s)
Log in to comment on this ticket.