You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "sudhakar (Jira)" <ji...@apache.org> on 2025/03/13 06:40:00 UTC
[jira] [Commented] (CASSANDRA-20434) Gpg Keys not imported, cannot verify repomd.xml for repo cassandra in amazon Linux2
[ https://issues.apache.org/jira/browse/CASSANDRA-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935072#comment-17935072 ]
sudhakar commented on CASSANDRA-20434:
--------------------------------------
The configuration we are using
{code:java}
[cassandra]
name=Apache Cassandra
baseurl=https://redhat.cassandra.apache.org/311x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://downloads.apache.org/cassandra/KEYS// code placeholder
{code}
> Gpg Keys not imported, cannot verify repomd.xml for repo cassandra in amazon Linux2
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-20434
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20434
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: sudhakar
> Priority: Normal
>
> Hi Team,
>
> While I was installing cassandra on amazon linux2 , i am facing issue while importing the keys
> {{sudo rpm --import https://downloads.apache.org/cassandra/KEYS
> error: https://downloads.apache.org/cassandra/KEYS: key 15 import failed.}}
> {{}}
> {{Our AMI builds from packer are also failing with below errors }}
> {code:java}
> // [0;32m2025-03-10T12:59:11Z: amazon-ebs.linux: Retrieving key from https://downloads.apache.org/cassandra/KEYS[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: https://redhat.cassandra.apache.org/311x/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo cassandra[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: Trying other mirror.[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: One of the configured repositories failed (Apache Cassandra),[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: and yum doesn't have enough cached data to continue. At this point the only[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: safe thing yum can do is fail. There are a few ways to work "fix" this:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: 1. Contact the upstream for the repository and get them to fix the problem.[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: 2. Reconfigure the baseurl/etc. for the repository, to point to a working[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: upstream. This is most often useful if you are using a newer[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: distribution release than is supported by the repository (and the[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: packages for the previous distribution release still work).[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: 3. Run the command with the repository temporarily disabled[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: yum --disablerepo=cassandra ...[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: 4. Disable the repository permanently, so yum won't use it by default. Yum[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: will then just ignore the repository until you permanently enable it[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: again or use --enablerepo for temporary usage:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: yum-config-manager --disable cassandra[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: or[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: subscription-manager repos --disable=cassandra[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: 5. Configure the failing repository to be skipped, if it is unavailable.[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: Note that yum will try to contact the repo. when it runs most commands,[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: so will have to try and fail each time (and thus. yum will be be much[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: slower). If it is a very temporary problem though, this is often a nice[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: compromise:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: yum-config-manager --save --setopt=cassandra.skip_if_unavailable=true[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux:[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: failure: repodata/repomd.xml from cassandra: [Errno 256] No more mirrors to try.[0m
> [1;31m2025-03-10T12:59:12Z: ==> amazon-ebs.linux: https://redhat.cassandra.apache.org/311x/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo cassandra[0m {code}
> Is there anything that recently changed for yum install and the repo data, can you guy's help me how we can fix this issue.
> Step for installing , the same steps worked earlier ,but I am seeing ami build failures recently.
>
> {{ sudo yum install java-1.8.0-openjdk -y
> sudo mv /tmp/files/cassandra-repo /etc/yum.repos.d/cassandra311x.repo
> sudo yum clean all
> sudo yum update -y
> sudo rpm --import https://www.apache.org/dist/cassandra/KEYS
> sudo yum install cassandra -y}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org