Hide Forgot
Description of problem: spacewalk20-client-centos6 fails to sync with "Channel does not exist or is not custom." Version-Release number of selected component (if applicable): How reproducible: everytime Steps to Reproduce: 1./usr/bin/spacewalk-repo-sync --channel=spacewalk20-client-centos6 2. 3. Actual results: "Channel does not exist or is not custom." Expected results: channel gets created Additional info: confirmed the channel exists in /usr/bin/spacewalk-common-channels --list | grep spacewalk20-client-centos6
>> spacewalk-common-channels --list | grep spacewalk2.*-client oraclelinux6-spacewalk22-client: i386, x86_64 oraclelinux6-spacewalk24-client: i386, x86_64 oraclelinux7-spacewalk22-client: x86_64 oraclelinux7-spacewalk24-client: x86_64 spacewalk24-client-opensuse_leap_42_1: x86_64 spacewalk25-client-centos6: i386, x86_64 spacewalk25-client-centos7: i386, x86_64 spacewalk25-client-oraclelinux6: i386, x86_64 spacewalk25-client-oraclelinux7: i386, x86_64 spacewalk25-client-scientific6: i386, x86_64 spacewalk26-client-centos6: i386, x86_64 spacewalk26-client-centos7: i386, x86_64 spacewalk26-client-fedora23: i386, x86_64 spacewalk26-client-fedora24: i386, x86_64 spacewalk26-client-opensuse_leap_42_2: x86_64 spacewalk26-client-oraclelinux6: i386, x86_64 spacewalk26-client-oraclelinux7: i386, x86_64 spacewalk26-client-scientific6: i386, x86_64 spacewalk27-client-opensuse_leap_42_3: x86_64
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.