I recently setup an Oracle Linux VM to be our spacewalk server after attending the HOL at openworld 16. I've got it working using an external oracle db and setup one base channel with multiple child channels as was shown in the lab.
Oracle Linux 6 Update 7 Installation media copy x86_64 23067
Dell DSU and OMSA for Linux 6 x86_64 0
Extra Packages for Enterprise Linux 6 x86_64 0
Ksplice for Oracle Linux 6 x86_640 Oracle Linux 6 Add ons x86_64 0
Oracle Linux 6 Update 7 Patches x86_64 0
Oracle Software for Oracle Linux 6 x86_64 0
Spacewalk Client 2.2 for Oracle Linux 6 0
UEK Release 3 for Oracle Linux 6 x86_64 0
Is this the right way to do this? one base channel with the rest as child because a spacewalk client can only subscribe to one base channel? These repos all sync to uln except for the epel and dell ones. when I tried syncing them all in the spacewalk gui by selecting the base channel then sync now it could not sync the 2 that were not uln. It errored out with "ERROR: url format error, url must start with uln://" so the non-uln repos must be synced separately from the uln ones? Is it better to use the taskomatic scheduler in the UI or just code a bunch of spacewalk-repo-sync jobs in cron? When I list out the repos with spacewalk-repo-sync -l the output looks odd to me.
======================================
| Channel Label | Repository |
======================================
ol6_u7_x86_64_base | http://linux.dell.com/repo/hardware/dsu/os_dependent/RHEL6_64/
ol6_u7_x86_64_base | http://download.fedoraproject.org/pub/epel/6/x86_64/
ol6_x86_64_spacewalk22_client | No repository set
epel_x86_64 | No repository set
ol6_x86_64_uekr3_latest | No repository set
dell_x86_64_omsa | No repository set
ol6_x86_64_ksplice | No repository set
ol6_u7_x86_64_patch | No repository set
ol6_x86_64_addons | No repository set
ol6_x86_64_oracle | No repository set
However in the UI the repos look fine and in the channel list they all appear as child channels under the base channel. I'm new to spacewalk and want to get it setup properly before I begin to sync our prod servers to it, appreciate any guidance I can get.