[Spacewalk-list] coreutils don't update properly via spacewalk

[Andy Ingham]

Thanks, Jan and Scott, for getting me on the right track.

Very helpful!

Andy


On 4/11/13 1:22 PM, "Scott Worthington" <scott.c.worthington at gmail.com>
wrote:

On 4/11/2013 10:42, Andy Ingham wrote:
> First, let me say that I am very willing to believe that my yum setup is
> sub-optimal for the spacewalk context, and appreciate help optimizing it.
>
> Having said that,
>
> We don't have any non-standard repos, generally, and for the clients I'm
> checking, there aren't any defined that aren't "spacewalk-managed".
>
> For that reason, we haven't set up the sort of "custom" setup that Scott
> describes below.
>
> What continues to confuse me about the issue is that:
>
> (a) when the coreutils packages are in need of updating, GUI-initiated
> updates from spacewalk don't work (but a local yum update does)
>
> (b) when the coreutils packages are NOT in need of updating,
>GUI-initiated
> updates from spacewalk DO work
>
> (Sure makes me think it is something specific to THOSE PACKAGES)
>
>
> I certainly see from that log entry that it is unhappy about the baseurl
> for "CentOS-Base", but my reading of the comments for that file
> (/etc/yum.repos.d/CentOS-Base.repo), indicate that I WANT the baseurl
> commented out:
>
> # The mirror system uses the connecting IP address of the client and the
> # update status of each mirror to pick mirrors that are updated to and
> # geographically close to the client.  You should use this for CentOS
> updates
> # unless you are manually picking other mirrors.
> #
> # If the mirrorlist= does not work for you, as a fall back you can try
>the
> # remarked out baseurl= line instead.
> #
>
>
>
>
> OR:
> Is it the case that for spacewalk-managed clients, there is no need for
> ANYTHING in /etc/yum.repos.d/ UNLESS it is a repo that spacewalk DOESN'T
> manage?
>
>
> Thanks again for help in quelling my confusion.
>
> Andy

Here are two references to previous discussions regarding this issue:

http://www.redhat.com/archives/spacewalk-list/2010-March/msg00000.html

http://www.redhat.com/archives/spacewalk-list/2009-December/msg00057.html

You typically disable all foreign yum repositories and allow only
Spacewalk/Satellite as your RPM source.
You do not enable both eternal repos and Spacewalk/Satellite channels at
the same time for the SAME source of repository files.

In a hybird setup where you are using both external repos and
Spacewalk/Satellite channels, you create the directory "mkdir -p
/etc/yum.repos.d/custom", place a symlink from
/etc/yum.repos.d/custom/<filename>.repo  back to the file in
/etc/yum.repos.d/<filename>.repo since repos rpms place their configs
into /etc/yum.repos.d/ (such as elrepo-release-6-5.elrepo.noarch.rpm
places its repository rpm into /etc/yum.repos.d/).  Finally, alter the
variable "reposdir" in /etc/yum.conf to be
"reposdir=/etc/yum.repos.d/custom/".

Yum updates will then pull from SW/SS and also from enternal repos
without problems (except when you need http_proxy/https_proxy settings
and that's a totally different issue).

Hope that helps.

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