Red Hat Bugzilla – Bug 1011934
taskomatic: repodata is not being regenerated for cloned channel
Last modified: 2015-10-09 04:42:50 EDT
Description of problem:
We lost all repodata files under /var/cache/rhn/repodata. Taskomatic create new repodata files for the original Base Channels, but not for our Cloned Channels.
We test it in Spacewalk 1.8 and taskomatic create the repodata files for all channel. As workaround we change the Repository Checksum Type and taskomatic create new repodata files.
All packages up2date.
Version-Release number of selected component (if applicable):
RedHat 6.3; 2.6.32-279.22.1.el6.x86_64
Steps to Reproduce:
Delete Cloned Channel repodata under /var/cache/rhn/repodata and restart taskomatic.
Repodata generation is triggered either when there's a change made to the channel, e.g. new package synced or repository checksum changed, or a client requests repodata from the channel and they aren't available.
So for cloned channels either cloning new package to it or access from a client should trigger repodata re-generation.
Yes, if the folder not exist the repodate will re-generated.
Sorry, I forgot the say if the files in the folder zero or corrupted nothing happens.