Created 04-03-2024 02:14 AM
Hello Community,
Installation is failing because of allkeys.asc not found...
This is not mentioned in the installation proccess and not additional config required, why is this happening and how to fix it?
why is this not mentioned in the documentation?
I can see the file there, is that a bug?
Thanks in advance
Created 04-03-2024 03:10 AM
Hello @Juanes
Yes it should be downloaded automatically in that case
As per the error in the attached screenshot it seems the URL is wrong the correct one should be https://archive.cloudera.com/p/cm7/7.7.1/ in your case it is pointing to https://archive.cloudera.com/cm7/7.7.1/allkeys.asc (/p is missing) which is causing issues
Created 04-03-2024 07:23 AM
Hello again,
I finally managed to pass by using "custom Repository" and adding the apropriate one, but the issue that I was facing was about using the first option "Cloudera Repository (direct Internet Access)".
this should be more automatic, or at least adding possible things to check, because it's not mentioned the allkeys.asc As i'm not using a web or local repo, i'm reaching directly the cloudera one.
Many thanks anyway 🙂
Created 04-03-2024 02:40 AM
Hello @Juanes
Thank you for bringing this
At this time, the documentation for setting up a local repo tells to download the repo-as-tarball file and untar that into the web server directory. If we follow this process, this will automatically include the allkeys.asc file, and therefore not have any problems.
If we do not follow the new documented process, and instead use the old process of recursive copying the archive, then it is possible that we will miss getting the keys file.
Yes there are some internal improvements JIRA raised to give more clarity on this to include the below as well in future versions
It is important to include the allkeys.asc file at the top level of the package repository. This file is included in the repo-as-tarball file. Be sure to include it if manually copying the package files between hosts.
The allkeys.asc file is used to validate the signatures of the package files during host installation. The add host workflow will fail if this file is not available in the repository.
Created 04-03-2024 02:55 AM
Hello,
First of all, thanks for your time.
then, i'm not creating a local repo, i'm using Cloudera repos with direct internet access, as I can see, the file is in the repo (in Cloudera) and this should be downloaded automatically I think...
Created 04-03-2024 03:10 AM
Hello @Juanes
Yes it should be downloaded automatically in that case
As per the error in the attached screenshot it seems the URL is wrong the correct one should be https://archive.cloudera.com/p/cm7/7.7.1/ in your case it is pointing to https://archive.cloudera.com/cm7/7.7.1/allkeys.asc (/p is missing) which is causing issues
Created 04-03-2024 07:23 AM
Hello again,
I finally managed to pass by using "custom Repository" and adding the apropriate one, but the issue that I was facing was about using the first option "Cloudera Repository (direct Internet Access)".
this should be more automatic, or at least adding possible things to check, because it's not mentioned the allkeys.asc As i'm not using a web or local repo, i'm reaching directly the cloudera one.
Many thanks anyway 🙂
Created 04-03-2024 05:51 PM
Hello @Juanes
Yes agreed we will need to find out why that URL was wrong
Anyways glad to know that the issue is resolved