Franky, I downloaded your script earlier today. On the first attempt, I was having the same issue, but then I decided to run separately against each child channel and it seems to be working.
Alan From: [email protected] [mailto:[email protected]] On Behalf Of Franky Van Liedekerke Sent: Friday, December 21, 2012 4:02 PM To: [email protected] Subject: Re: [Spacewalk-list] converting from get_errata.pl to eva-direct-errata-sync.pl Maybe you can try my errata script: https://github.com/liedekef/spacewalk_scripts . It had been working for many months at the company I'm working now, for a combo of redhat and centos channels, land using a proxy. It's easy to use and gets the job done. Franky Alan Pittman <[email protected]<mailto:[email protected]>> schreef: Based on the reply below, I decided to spend all day Thursday adding the additional RHEL channels and sync-ing them up. Then I re-ran the eva-direct-errata-sync.pl program/script. After letting it run all night (or however long it took), I logged on to the GUI and went to the errata screen. Selected "all" and nothing was displayed. See the attached jpeg. When I ran the errata-sync script, I redirected all of standard out to a file in /tmp. Reviewing the file showed hundreds of messages like this: checking if RHSA-2012:1483 exists on the destination host Getting details for RHSA-2012:1483 getting RHSA-2012:1483 from the source Getting details for RHSA-2012:1483 Skipping errata RHSA-2012:1483 because none of its packages could be found in the destination channels Based on your reply, it makes sense that the older errata would and should be skipped. However, using the errata listed above (RHSA-2012:1483), I did some research. When I look up this one on the Red Hat Customer Portal, it’s for Thunderbird. Specifically for packages: RHEL Optional Productivity Applications (v. 5 server) IA-32: thunderbird-10.0.11-1.el5_8.i386.rpm x86_64: thunderbird-10.0.11-1.el5_8.x86_64.rpm Red Hat Enterprise Linux Server (v. 6) ________________________________ SRPMS: thunderbird-10.0.11-1.el6_3.src.rpm MD5: ff2af052f366c47bc2dc85a678be69fa SHA-256: fcab1a66282f61f1c7d70ef0a1510c26192efe336fd00a32f7dba384b1551b4b IA-32: thunderbird-10.0.11-1.el6_3.i686.rpm MD5: 086fd6f439cf7c5b72ce26569c36fa0f SHA-256: fc22b80774490a0ee135dd3d955faa402fd4b93379c915706009acfc7e3b173b thunderbird-debuginfo-10.0.11-1.el6_3.i686.rpm I then looked up thunderbird in the GUI and found the same rpms (see the Thunderbird gif image). So, I guess I’m not understanding standing. Is there something I’m missing? Is there some additional debugging options/parameters that I can turn on (I’m not a perl expert) that might help me debug this problem? Alan -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Paul Robert Marino Sent: Wednesday, December 19, 2012 5:29 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Spacewalk-list] converting from get_errata.pl to eva-direct-errata-sync.pl well these are a common question first when you go int errata are you looking at the all or relevant page which is the default go into ERRATA -> All to see them all if you just go into ERRATA you are viewing the Relevant page which only shows you erratas that apply to systems that have not been patched yet. this message " Skipping errata RHSA-2007:0153 because none of its packages could be found in the destination channels " there are no rpms in any of the channels that match the rpms in any of the repos that match the ones in the errata in this case its an errata from 2007 which has probably long since been deprecated by a newer errata and Redhat only keeps a few previous versions of an rpm in RHN so your spacewalk server probably had any of those rpms and never will. so eva-direct-errata-sync.pl does not publish them because essentially they are useless. its also a safety in case your repos are out of sync with RHN; because eva-direct-errata-sync.pl will not update an already published errata. On Wed, Dec 19, 2012 at 2:03 PM, Alan Pittman <[email protected]<mailto:[email protected]>> wrote: > Hi, > I am in the processing of setting up a new Spacewalk server for my RHEL > machines. My current server is scheduled to be retired sometime in 2013. I > am running RHEL6.3 and using Spacewalk 1.7. On my current machine, I run > get_errata.pl. It works, but it’s really slow. On my new machine, I would > like to use eva-direct-errata-sync.pl. > > I just completed a test run with eva-direct and it seemed to run to > completion, but it never loaded anything into Spacewalk. At least, when I > logon and click on Errata, nothing appears. Reviewing the output I see allot > of the following: > > checking if RHSA-2007:0153 exists on the destination host > Getting details for RHSA-2007:0153 > getting RHSA-2007:0153 from the source > Getting details for RHSA-2007:0153 > Skipping errata RHSA-2007:0153 because none of its packages could be found > in the destination channels > checking if RHSA-2007:0157 exists on the destination host > Getting details for RHSA-2007:0157 > getting RHSA-2007:0157 from the source > Getting details for RHSA-2007:0157 > getting details for package xorg-x11-apps > getting details for package xorg-x11-apps > Skipping errata RHSA-2007:0157 because none of its packages could be found > in the destination channels > checking if RHSA-2007:0123 exists on the destination host > Getting details for RHSA-2007:0123 > getting RHSA-2007:0123 from the source > Getting details for RHSA-2007:0123 > Skipping errata RHSA-2007:0123 because none of its packages could be found > in the destination channels > > Here’s the script and the options that I used: > > #/bin/bash > > /usr/bin/perl /usr/local/sbin/eva-direct-errata-sync.pl \ > --sourceuser=AAAAAA \ > --destinationuser=BBBBBBBB \ > --sourcepassword=XXXXXXXXXX \ > --destinationpassword=ZZZZZZZZZZ \ > --sourcechannel=rhel-i386-server-5 \ > --destinationchannel=rhel-i386-server-5 \ > --sourceserver=rhn.redhat.com \ > --destinationserver=localhost \ > --recursive \ > --verbose > > Here’s my Spacewalk channel structure: > Parent: > Channel name: rhel-i386-server-5 Channel Label: rhel-32bit-server-5 > Children: > Channel name: rhel-i386-server-5-rhn-tools > Channel label: rhel-32bit-server-5-rhn-tools > Channel name: rhel-i386-server-5-spacewalk-client-1.7 Channel label: > rhel-32bit-server-5-spacewalk-client-1.7 > Channel name: rhel-i386-server-5-supplementary Channel > label: rhel-32bit-server-5-supplementary > Channel name: rhel-i386-server-5-updates > Channel label: rhel-32bit-server-5-updates > > The same structure exists for RHEL5-x86_64 and both RHEL6 channels. > > I use mrepo to get the packages and I use spacewalk-repo-sync to load them. > Here’s an example: > > /usr/bin/spacewalk-repo-sync --channel rhel-32bit-server-5-rhn-tools --type > yum > > In the channels I have the following number of packages: > rhel-i386-server-5-rhn-tools 233 > rhel-i386-server-5-spacewalk-client-1.7 21 > rhel-i386-server-5-supplementary 93 > rhel-i386-server-5-updates 2559 > > If anyone has any suggestions as to what I can look at to determine what’s > wrong, I would appreciate it. > > Alan > > > Alan Pittman > Publix Super Markets, Inc > 863-686-8754 x46320 > [email protected]<mailto:[email protected]> > > Unix is user-friendly. It's just very selective about who its friends are. > > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected]<mailto:[email protected]> > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list ________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
