[
https://issues.apache.org/jira/browse/CASSANDRA-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931552#comment-17931552
]
Brandon Williams commented on CASSANDRA-20369:
----------------------------------------------
Hmm, well, happy to fix whatever is wrong if we can figure out what that is.
Meanwhile this seems to be working for others.
> Cassandra RPM repository not valid GPG key for AL2
> --------------------------------------------------
>
> Key: CASSANDRA-20369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20369
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: Dipietro Salvatore
> Priority: Normal
>
> We are trying to use the Cassandra repository for Cassandra 41x and 50x on
> Amazon Linux 2 but there are some issues with the key validation. Can you
> please fix it?
> Here the error message:
> {code:java}
> https://redhat.cassandra.apache.org/41x/noboolean/repodata/repomd.xml:
> [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo cassandra
> Trying other mirror.
>
>
> One of the configured repositories failed (Apache Cassandra),
> 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=cassandra ...
>
> 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 cassandra
> or
> subscription-manager repos --disable=cassandra
>
> 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=cassandra.skip_if_unavailable=true
>
> failure: repodata/repomd.xml from cassandra: [Errno 256] No more mirrors
> to try.
> https://redhat.cassandra.apache.org/41x/noboolean/repodata/repomd.xml:
> [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo cassandra
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
