[Spacewalk-list] Fix yum repo definitions on spacewalk clients
William H. ten Bensel
WHTENBEN at up.com
Tue Feb 13 19:11:33 UTC 2018
http://spacewalk-list.redhat.narkive.com/aBoQIh6I/rhn-check-fails
snippet --> As of 02/13/2018 --> We have not found a better solution..
We ran into issues where "yum update" updated the centos-release RPM,
which in turn would push updated .repos to /etc/yum.repos.d/. This would
cause a similar issue to the errors described.
The solution we came up with, was to put the following in the post section
of the default kickstart: If there is a better idea, I am all ears.
mkdir -p /some/where/
echo "reposdir=" /some/where/" >> /etc/yum.conf
Some benefits, by doing this has been that 3rd party vendor apps that
install their own /etc/yum.repos.d/ will not cause any delays or issues
with running yum commands (if they cannot reach the site). If the client
is able to reach the site, then a request process will move the 3rd party
.repo in /some/where.
Thanks and good luck
From: Isaac Hailperin <Isaac.Hailperin at lcsystems.ch>
To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
Date: 02/13/2018 01:28 AM
Subject: Re: [Spacewalk-list] Fix yum repo definitions on spacewalk
clients
Sent by: spacewalk-list-bounces at redhat.com
This email originated from outside of the company. Please use discretion
if opening attachments or clicking on links.
Bruce – thank you for the hint to just disable the repos – of course, now
that you mention it its crystal clear J
Isaac
From: spacewalk-list-bounces at redhat.com [
mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Bruce Wainer
Sent: Montag, 12. Februar 2018 16:53
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Fix yum repo definitions on spacewalk
clients
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.Hailperin at 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 at 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-bounces at redhat.com [spacewalk-list-bounces at redhat.com
]" im Auftrag von "Avi Miller [avi.miller at oracle.com]
Gesendet: Montag, 12. Februar 2018 16:30
An: spacewalk-list at 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.Hailperin at 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
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
[attachment "smime.p7s" deleted by William H. ten Bensel/UPC]
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
**
This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20180213/ae9d3a42/attachment.htm>
More information about the Spacewalk-list
mailing list