Jan -- These are CentOS 6.4 servers (upgraded from 6.3 within the last few weeks) & they only had a few packages that needed updating today, chief among them the "coreutils" and "coreutils-libs" packages.
Spacewalk server is at version 1.8 rhn-client-tools is 1.8.26-1.el6 (systematically updated across the plant right after the spacewalk server upgrade) I'm scheduling updates via the Spacewalk GUI, and they fail with (the ever present) "Fatal error in Python code occurred [[6]]". As I say, once I update the coreutils and coreutils-libs packages manually, GUI-initiated updates generally run fine. Andy On 4/9/13 12:17 PM, "Jan Pazdziora" <[email protected]> wrote: On Tue, Apr 09, 2013 at 01:47:15PM +0000, Andy Ingham wrote: > Looking for a sanity check here. > > Certain packages won't update properly via spacewalk UNTIL "coreutils" is > updated on that client. > > The problem is that I'm unable to get the coreutils packages THEMSELVES >to > update via spacewalk. > > So, I find myself having to connect to each client individually to "yum > update coreutils". > > At that point, I'm having success pushing updates to the clients that > failed previously. > > Of course, given those steps, I've not saved any time since I've already > had to connect to each client. > > Am I missing something about how to avoid this? Can you be more specific about the exact OS you're using, Spacewalk server version, RHN client tools version, as well as the exact commands you run and the output you get? -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
