Avi - interesting point:
# yum repolist |grep epel
 * epel: mirror.de.leaseweb.net
epel/x86_64                        Extra Packages for Enterprise Linux 7  12,278
!epel7-centos7-x86_64              EPEL 7 for CentOS 7 (x86_64)           13,357

I think the latter is the one defined in spacewalk. However there seems to be 
not corresponding yum repo in /etc/yum.repos.d - is that how it should be?
So all I would need to to is delete the local definition of epel?

Isaac

________________________________
Von: spacewalk-list-boun...@redhat.com [spacewalk-list-boun...@redhat.com]" im 
Auftrag von "Avi Miller [avi.mil...@oracle.com]
Gesendet: Montag, 12. Februar 2018 16:30
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Fix yum repo definitions on spacewalk clients

Hi,


On 12 Feb 2018, at 11:51 am, Isaac Hailperin 
<isaac.hailpe...@lcsystems.ch<mailto:isaac.hailpe...@lcsystems.ch>> wrote:

What would be the easiest, or most reliable way to get the correct repo 
definitions back?

There may be a misunderstanding here, but Spacewalk does not generate anything 
in /etc/yum.repos.d/. You don't see any repo definitions on the client side, 
it's all done in Spacewalk.

What is the output of "yum repolist" on a client after it has registered with 
Spacewalk? If there are channels associated with the activation key you used, 
they should be automatically enabled. If not, you may have to enable the 
channels manually via the web UI or spacecmd.

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to