Hi all,

We have an issue that the repo was updated and now we cannot verify the GPG key, when trying to install we get this error

` One of the configured repositories failed (openresty),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=openresty ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable openresty
    or
        subscription-manager repos --disable=openresty

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=openresty.skip_if_unavailable=true

failure: repodata/repomd.xml from openresty: [Errno 256] No more mirrors to try.`

    5 days later

    I'll confirm I'm also running into the issue on CentOS7.
    Looks like some of the repodata was recently changed but not the .asc at https://openresty.org/package/centos/7/x86_64/repodata/ so that might have something to do with it:

    0a30b5c81f4b71a7f7ddf66778506c3e9c8a5cba14969fb..> 04-Nov-2022 22:30               14806
    2ede3ad09a5ceaf85eb6b6ae548ddf2a0f058e803a6d651..> 04-Nov-2022 22:30               42384
    35b8c3c1f206eca4c4cf659a184c20de19ddcb4c8d66af4..> 04-Nov-2022 22:30               28522
    d2dde2025daa540a63ff209f4ec559b8839f5c5fa5cd4f4..> 04-Nov-2022 22:30               84561
    dee3d7f5f1164c68b2dd2d4685f082e6013d2b7fd65be34..> 04-Nov-2022 22:30               57380
    eec00fc288fd09a14a012da367420e0579115fceec4f970..> 04-Nov-2022 22:30               34291
    repomd.xml                                         04-Nov-2022 22:30                2987
    repomd.xml.asc                                     17-May-2022 19:46                 490

    One can set repo_gpgcheck=0 in the repo file as a workaround, but I'd like to see this fixed as well.

      Write a Reply...