I recently installed Spacewalk 1.7 and Create new channel.
I am having an issue where I cannot get a system that is subscribed to the
new channel to update any packages. There seems to be an issue with the
channel config. When I run a “yum list” command on the client of the new
channel I get the f
Is the time set right on the client? I was having a similar problem and
it was due to time and the ssl certificate.
On 04/28/2012 08:23 AM, Kazi Hossain wrote:
I recently installed Spacewalk 1.7 and Create new channel.
I am having an issue where I cannot get a system that is subscribed to
t
Hey Kazi,
Did you ever get this worked out? I'm in a similar boat with spacewalk 1.7
w/ postgresql.
I can successfully add a client, and it checks in, but when I do any yum
functions, it barfs with the same error as you. I checked time and I am not
using ssl so that isn't the problem for me.
Wha
Deployed a new machine, it didn't have internet access, added manually epel
repo & spacewalk repo and installed client, registered on the spacewalk.
The system shows this error, when I try to do anything:
Cannot retrieve repository metadata (repomd.xml) for repository:
epel_sci_6. Please verify i
I had a similar issue for systems that had old versions of nss, they
couldn't deal with an HTTPS repo for some reason. Is your
/etc/sysconfig/rhn/up2date pointing to https://something by chance? If so
try changing it to http, updating yum and nss fully, then changing it back
to https.
One liner:
The problem is - my servers don't have internet access. I set up epel repo
sync on spacewalk...For example epel
[epel]
name=Extra Packages for Enterprise Linux 6 - $basearch
baseurl=https://spacewalk/repos/epel6/x86_64/
#mirrorlist=
https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$bas
Oh, that error you're seeing is because your system(s) don't recognize the
SSL cert generated by Spacewalk. In your bootstrap script, is the
RHN-ORG-TRUSTED-CERT (or something like that) being pushed correctly to the
clients? Otherwise they won't recognize the SSL cert being presented by
your Spa
Eventually this script fixed all the stuff :).
rpm -Uvh
http://spacewalk/repos/spacewalk_client6/2.3-client/RHEL/6/x86_64/spacewalk-client-repo-2.3-2.el6.noarch.rpm
rpm -Uvh http://spacewalk/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
cat > /etc/yum.repos.d/spacewalk-client.repo << EOF
[spacewal
Great, yeah that stuff is usually taken care of in the bootstrap, which is
how we register our systems to Spacewalk initially. The hard part is when
we have to reregister systems after they already have
/etc/sysconfig/rhn/systemid and so on... but that's another story.
On Thu, Mar 31, 2016 at 4:4
