Follow the steps bellow on your Red Hat Satellite server to force repodata generation for any problematic channel.

• Schedule repodata re-generation task for taskomatic daemon using API:

# spacewalk-api --server=<your Satellite FQDN> --user=<admin user> --password=< paswword> channel.software.regenerateYumCache %session% <Channel Label>

 

Note: Replace satellite server hostname , username/password and channel label with proper values. If there is more than one affected channel, then run this command multiple time with different channel labels.

For eg: To re-generate repodata for rhn-tools-rhel-x86_64-server-6 channel you can use this command:

# spacewalk-api --server=satellite.example.com --user=admin --password=secret channel.software.regenerateYumCache %session% rhn-tools-rhel-x86_64-server-6

 

• Force execution of the scheduled task

- Login to `RH Satellite` WebUi
- Click on `Admin` tab
- Click on `Task Schedules` on left hand menu
- Click on `Channel-repodata-bunch`
- Click on button "Single Run Schedule"

 

• Monitor /var/log/rhn/rhn_taskomatic_daemon.log file for progress in repodata re-generation and confirm whether repodata files got created under /var/cache/rhn/repodata/channel-label directory or not.

# ls -l /var/cache/rhn/repodata/<channel-label>

 

Initially we can see files with .new extension which means that repodata re-generation is in progress. Once .new extension is removed which means that repodata generation is completed.

• After the above steps are completed you can run the below mentioned commands on the client and confirm Channel contents are available to the client or not:

# yum clean all
# yum repolist

 

 

<< Source : Redhat Solution 319983 >>