problem in setting up some Intel repositories - signature could not be verified for intel-clck-ext-2

[ndry]

We are having a similar issue as what is mentioned in this question https://community.intel.com/t5/oneAPI-Registration-Download/yum-y-install-intel-mkl-64bit-2020-0-088-fails-due-to-repomd-xml/m-p/1531690, but the answer is hidden for some reason in private messaging so we can't see how it was resolved.  Can you please share the solution with us as well?

[ec2-user@ip-10-0-0-21 ~]$ sudo yum-config-manager --add-repo https://yum.repos.intel.com/clck-ext/2019/setup/intel-clck-ext-2019.repo
Loaded plugins: dkms-build-requires, extras_suggestions, langpacks, priorities, update-motd, versionlock
adding repo from: https://yum.repos.intel.com/clck-ext/2019/setup/intel-clck-ext-2019.repo
grabbing file https://yum.repos.intel.com/clck-ext/2019/setup/intel-clck-ext-2019.repo to /etc/yum.repos.d/intel-clck-ext-2019.repo
repo saved to /etc/yum.repos.d/intel-clck-ext-2019.repo

[ec2-user@ip-10-0-0-21 ~]$ sudo rpm --import https://yum.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB

[ec2-user@ip-10-0-0-21 ~]$ sudo yum install intel-clck-hpc-platform
Loaded plugins: dkms-build-requires, extras_suggestions, langpacks, priorities, update-motd, versionlock
amzn2-core                                              | 3.6 kB  00:00:00
amzn2extra-R3.4                                         | 3.0 kB  00:00:00
amzn2extra-docker                                       | 3.0 kB  00:00:00
amzn2extra-epel                                         | 3.0 kB  00:00:00
amzn2extra-kernel-5.10                                  | 3.0 kB  00:00:00
amzn2extra-lustre                                       | 3.0 kB  00:00:00
amzn2extra-python3.8                                    |  25 kB  00:00:00
epel                                                    | 4.7 kB  00:00:00
intel-clck-ext-2019-repo/signature                      |  287 B  00:00:00
Retrieving key from https://yum.repos.intel.com/clck-ext/2019/setup/PUBLIC_KEY.PUB
Importing GPG key 0x1911E097:
 Userid     : ""CN = Intel(R) Software Development Products", O=Intel Corporation"
 Fingerprint: bf43 85f9 1ca5 fc00 5ab3 9e1c 1a84 97b1 1911 e097
 From       : https://yum.repos.intel.com/clck-ext/2019/setup/PUBLIC_KEY.PUB
Is this ok [y/N]: y
intel-clck-ext-2019-repo/signature                                                                                                                                     | 1.1 kB  00:00:12 !!!
https://yum.repos.intel.com/clck-ext/2019/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for intel-clck-ext-2019-repo
Trying other mirror.

 One of the configured repositories failed (Intel(R) Cluster Checker Select Solutions Extensions 2019),
 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:
...
failure: repodata/repomd.xml from intel-clck-ext-2019-repo: [Errno 256] No more mirrors to try.
https://yum.repos.intel.com/clck-ext/2019/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for intel-clck-ext-2019-repo

[RahulC_Intel]

Hi Ryan, please note that Intel® has decided that Intel® oneAPI Toolkits Versions: 2023.1.0 and earlier are not supported anymore. We urge users to upgrade to the latest version of Intel® developer tools.

The unsupported versions do not include the latest functional and security updates. These versions are targeted to be removed after a period. For more information refer to the link: https://www.intel.com/content/www/us/en/developer/articles/release-notes/oneapi-supported-product-versions.htm, and scroll down to the Unsupported Product Versions. Kindly note that the support is limited for older versions.

You may refer to the link: https://www.intel.com/content/dam/develop/external/us/en/documents/clck-release-notes-2019-9.pdf for further help.

[RahulC_Intel]

Hi Ryan, unfortunately we were unable to hear back from you. 

If you have any further query, please post a new question as this thread will no longer be monitored by Intel®.