[Spacewalk-list] Channels::Manage Software Channels::Manage Software Packages "channel" picklist

[Kennedy, Ryan]

I deleted my EPEL channel and deleted its orphaned packages from Spacewalk.
Then I re-added the channel and did a CLI reposync with...
reposync --arch=x86_64 --repoid=epel -p /var/www/html/pub/CentOS5-x86_64 -d -l -g -n -q > /dev/null
cd /var/www/html/pub/CentOS5-x86_64/epel
createrepo /var/www/html/pub/CentOS5-x86_64/epel > /dev/null
/usr/bin/spacewalk-repo-sync --channel epel5-x86_64 \
                             --url file:///var/www/html/pub/CentOS5-x86_64/epel/ \
                             --type yum --label epel5-x86_64 > /dev/null

I got a bunch of python errors for what seemed like every package it was syncing.
Here's an example...
> Exception reported from spacewalk01.paml.com
> Time: Thu Feb 11 10:12:25 2010
> Exception type server.importlib.importLib.InvalidPackageError
>
> Exception Handler Information
> Traceback (most recent call last):
>    File "/usr/share/rhn/satellite_tools/reposync.py", line 157, in import_packages
>      self.associate_package(pack, md5)
>    File "/usr/share/rhn/satellite_tools/reposync.py", line 199, in associate_package
>      self._importer_run(package, caller, backend)
>    File "/usr/share/rhn/satellite_tools/reposync.py", line 207, in _importer_run
>      importer.run()
>    File "/usr/share/rhn/server/importlib/importLib.py", line 628, in run
>      self.submit()
>    File "/usr/share/rhn/server/importlib/packageImport.py", line 114, in submit
>      self.backend.lookupPackages(self.batch)
>    File "/usr/share/rhn/server/importlib/backend.py", line 519, in lookupPackages
>      self.__lookupObjectCollection(packages, 'rhnPackage', ignore_missing)
>    File "/usr/share/rhn/server/importlib/backend.py", line 1771, in __lookupObjectCollection
>      raise InvalidPackageError(object, "Could not find object %s in 
> table %s" % (object, tableName))
> InvalidPackageError: Could not find object 
> [<server.importlib.importLib.IncompletePackage instance; 
> attributes={'package_size': None, 'package_arch_id': 100, 'name': 
> 'perl-DateTime-Format-W3CDTF', 'md5sum': 
> 'efeb11a8d0ef1fea4cd657cadb807a09', 'org_id': '1', 'package_id': None, 
> 'channels': {146: 'epel5-x86_64'}, 'nevra_id': 7124, 'epoch': '', 
> 'version': '0.04', 'name_id': 2850, 'last_modified': None, 'release': 
> '1.el5', 'arch': 'noarch', 'evr_id': 2611}] in table rhnPackage

95 out of the 97 packages I have defined in the epel repo conf ended up orphaned but two were actually assigned to the EPEL channel.  Weird.  I went ahead and just added them to EPEL via the spacewalk gui at that point.  Easy enough, but the "channel" picklist under "Manage Software Packages" has a bizarre ordering of its items now.

It looks like this:
-------------------------------
  All managed packages
  Packages in no channels
    EPEL 5 - x86_64
  Centos 5 Base - x86_64
    RPMforge EL5 - x86_64
    Centos 5 Updates - x86_64
    Spacewalk - x86_64
--------------------------------

The EPEL channel DEFINITELY has "Centos 5 Base - x86_64" as its parent channel so I am mystified why it would look like this or if its even a problem.  I was able to install packages in EPEL on a client just fine so it seems fairly benign.  Also, I have since added an additional 3 packages to my EPEL repo conf file and run the script but w/o any python errors so it looks like that might have been a one-time fluke.  Anyone have any suggestions?

--
Ryan Kennedy | PAML | Systems Administrator III
Desk: 509.755.8499 | Fax: 509.209.5499


DISCLAIMER:
Information contained in this message may be privileged and confidential. 
If the reader of this message is not the intended recipient, be notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If this communication is received in error, please 
notify the sender immediately by replying to the message and deleting 
from your computer. Thank you