Re: BUG #18352: signature could not be verified for pgdg-common

From: Michael Johnson <michael(at)letsengage(dot)com(dot)au>
To: michael(at)letsengage(dot)com(dot)au, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18352: signature could not be verified for pgdg-common
Date: 2024-02-20 22:27:38
Message-ID: CAMwmMmj_cFPjz3se6vva1apEdP+c7L-_fV_T4e26Nv9zb9R3qQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The initial error presented was from our EL7 mirror, but the error is also
encountered on our EL8 mirror.

dnf reposync returns: Error: Failed to download metadata for repo
'pgdg-common': repomd.xml GPG signature verification error: Bad GPG
signature

On Tue, 20 Feb 2024 at 16:30, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18352
> Logged by: Michael Johnson
> Email address: michael(at)letsengage(dot)com(dot)au
> PostgreSQL version: 12.17
> Operating system: RHEL 8.8
> Description:
>
> Error setting up repositories: failure: repodata/repomd.xml from
> pgdg-common: [Errno 256] No more mirrors to try.
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__download.postgresql.org_pub_repos_yum_common_redhat_rhel-2D7Server-2Dx86-5F64_repodata_repomd.xml&d=DwIGaQ&c=NxS7LVD4EucgUR9_G6bWzuqhmQ0xEJ2AZdqjz4WaSHU&r=9BG2oV86MrHbxzHVaZTbDRFnTrmH5vowUyudyHoFxi0&m=kJ2oCumDWs-vAW_LlA0lNHR8MW-_EXVBi3BELXncmr95J-Q4vF5ZDWwKH-5coOxj&s=HaD2CgInjs34z_Wl1SXKxwLWFCeDzjMcKxPRjflrivA&e=
> :
> [Errno -1] repomd.xml signature could not be verified for pgdg-common
>
> After receiving this error, I made sure the GPG Key was up to date and it
> still occurs. It was working when we checked last month.
>
>

--
This message may contain confidential and/or privileged information. 
If
you are not the addressee or authorized to receive this on behalf of the
addressee you must not use, copy, disclose or take action based on this
message or any information herein. 
If you have received this message in
error, please advise the sender immediately by reply email and delete this
message. Thank you.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-02-21 12:00:01 BUG #18354: Aborted transaction aborted during cleanup when temp_file_limit exceeded
Previous Message Tom Lane 2024-02-20 20:56:04 Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);