The yum-rhn-plugin loads them directly from Spacewalk I believe, or maybe
its cached during an rhn_check - not sure which. That is why when you run
any Yum command it prints out the line about "This server is receiving
updates from a Spacewalk system" or something like that (don't have a
terminal open right now). By the way, don't delete your .repo files,
because updates to things like epel-release, zfs-release, etc will just
create them again. Instead, disable all of the repos. This is what I run on
each system as part of my registration process:

#sed -i 's/enabled=1/enabled=0/' /etc/yum.repos.d/*.repo

Bruce Wainer

On Mon, Feb 12, 2018 at 10:42 AM, Isaac Hailperin <
isaac.hailpe...@lcsystems.ch> wrote:

> Ok, just verified: If I remove the .repo file for epel, the "epel/x86_64"
> is gone. But how does yum know about the other repository? Where is that
> defined? Does yum have a plugin that lets it query the correct repositories
> directly from spacewalk?
>
> Isaac
> ------------------------------
> *Von:* Isaac Hailperin
> *Gesendet:* Montag, 12. Februar 2018 16:39
> *An:* spacewalk-list@redhat.com
> *Betreff:* AW: [Spacewalk-list] Fix yum repo definitions on spacewalk
> clients
>
> 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-bounces@
> 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>
> 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
> <+61%203%208616%203496>
> Oracle Linux and Virtualization
> 417 St Kilda Road, Melbourne, Victoria 3004 Australia
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to