spacewalk-repo-sync fails with "Channel does not exist or is not custom" error while syncing EPEL repositories

Solution Verified - Updated -

Environment

  • Red Hat Satellite 5.6

Issue

  • Below crontab fails with error Channel does not exist or is not custom
/usr/bin/spacewalk-repo-sync --channel epel_rhel5_x86_64 --url http://<Mirror_fqdn>/fedora-epel/5Server/x86_64/ --type yum >/var/log/rhn/epel_rhel5_sync.log 2>&1

Resolution

The channel's label must be used with the --channel= flag not the channel name. The 'channel label' can be found in the WebUi under the Channels ---> Manage Software Channels ---> . On this overview page you should see the channel label.

Diagnostic Steps

  • Check output of spacewalk-report custom-channels command
  • Get the channel id and then check if that channel is listed at RHNCHANNELFAMILYMEMBERS table.
    NOTE: Please replace Channel label and Channel_id with appropriate values.
rhnschema=# select id, label from rhnChannel where label = 'epel_rhel5_x86_64';

 id  |       label
-----+-------------------
 106 | epel_rhel5_x86_64
(1 row)

rhnschema=# select * from RHNCHANNELFAMILYMEMBERS where channel_id = '106';
 channel_id | channel_family_id | created | modified
------------+-------------------+---------+----------
(0 rows)

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments