Error on applying highstate after 2023.01 update - tries to pull repomd.xml.key from external url
After the 2023.01 update, I've had a couple of issues. Abid was able to help me (I think) resolve the issue with the channel listing in the web ui. Now, I noticed that an Oracle Linux 8 system that is newly added will give an error with applying the highstate. It appears to be trying to pull the repo key from the original location on the internet, instead of from the Uyuni server, from the managed system. The repositories added are the base channel, appstream, and the uyuni client tools. The error is coming from the Uyuni client tools. It seems that the managed system is trying to pull the repo key from an external URL (where Uyunio syncs this down from), and timing out. What could be going on that is causing this behavior? I would assume that it would pull that from the Uyuni server, itself. Thanks. ID: https_//download.opensuse.org/repositories/systemsmanagement_/Uyuni_/Stable_/CentOS8-Uyuni-Client-Tools/CentOS_8/repodata/repomd.xml.key Function: mgrcompat.run Name: pkg.add_repo_key Result: false Comment: Module function pkg.add_repo_key threw an exception. Exception: Error: HTTP 599: Timeout while connecting reading /repositories/systemsmanagement:/Uyuni:/Stable:/CentOS8-Uyuni-Client-Tools/CentOS_8/repodata/repomd.xml.key Started: 12:59:38.991575 Duration: 20023.057 SLS: channels.gpg-keys Changed: {} -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen@ua.edu
Okay, so I have done some digging, and it looks like that URL it is trying to load is specified under the GPG section of the config for that channel. It looks like the others are set to the file:///etc/pki/rpm-gpg/ directory, and the key that is referenced at that URL is in that directory.
I'm assuming that I should edit that channel, and point it to that location? Will try and see if that resolves the problem.
Allen B.
--
Allen Beddingfield
Systems Engineer
Office of Information Technology
The University of Alabama
Office 205-348-2251
allen@ua.edu
________________________________________
From: Allen Beddingfield
participants (1)
-
Allen Beddingfield