[Spacewalk-list] trick to doing CentOS 6.3 > 6.4 update via spacewalk?

[Andy Ingham]

Thanks, everyone, for the lively discussion!

I'm still relatively new to spacewalk (less than a year) and have never
set up any channels beyond the default ones I originally created with the

	/usr/bin/spacewalk-common-channels

command.  Thanks for the ideas of some things to try.



As for what happens when I kick off a full update (selecting all 290+
packages in the GUI), the action is picked up quickly, rhn_check runs for
a LONG time on the client (~ 2.5 hours) and then the action fails with:

Error while executing packages action: Error Downloading Packages:
tcsh-6.17-24.el6.x86_64: failure: Packages/tcsh-6.17-24.el6.x86_64.rpm
from base: [Errno 256] No more mirrors to try. gawk-3.1.7-10.el6.x86_64:
failure: Packages/gawk-3.1.7-10.el6.x86_64.rpm from base: [Errno 256] No
more mirrors to try. strace-4.5.19-1.17.el6.x86_64: failure:
Packages/strace-4.5.19-1.17.el6.x86_64.rpm from base: [Errno 256] No more
mirrors to try. plymouth-graphics-libs-0.8.3-27.el6.centos.x86_64:
failure: Packages/plymouth-graphics-libs-0.8.3-27.el6.centos.x86_64.rpm
from base: [Errno 256] No more mirrors to try.
krb5-libs-1.10.3-10.el6.x86_64: failure:
Packages/krb5-libs-1.10.3-10.el6.x86_64.rpm from base: [Errno 256] No more
mirrors to try. glibc-2.12-1.107.el6.x86_64: failure:
Packages/glibc-2.12-1.107.el6.x86_64.rpm from base: [Errno 256] No more
mirrors to try. cifs-utils-4.8.1-18.el6.x86_64: failure:
Packages/cifs-utils-4.8.1-18.el6.x86_64.rpm from base: [Errno 256] No more
mirrors to try. mtdev-1.1.2-5





Andy



On 3/12/13 4:08 AM, "Jan Pazdziora" <jpazdziora at redhat.com> wrote:

On Mon, Mar 11, 2013 at 07:02:50PM +0000, Andy Ingham wrote:
> Friendly list --
> 
> Now that CentOS 6.4 is available, I have 40+ servers that I'd like to
> update from 6.3 > 6.4.
> 
> I just finished bringing all the (spacewalk-managed) servers up to date
> with osad, rhn-check, rhn-client-tools, rhn-setup, rhnlib, etc.  (I'm at
> version 1.8 still.)
> 
> Scheduling the update via spacewalk results in a failure, though.

Is the failure manifested somehow, perhaps by an error message which
could help the audience help you to figure out what is wrong?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

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