Description of problem: If a user syncs RHEL 5 s390x kickstart tree content to a 530 Satellite (via the server and rhn-tools channels), the tree will not sync to Cobbler, with the following error appearing in the Taskomatic log: 1 [DefaultQuartzScheduler_Worker-1] ERROR com.redhat.rhn.manager.kickstart.cobbler.CobblerDistroSyncCommand - ERROR: No kernel found in this path: [/var/satellite/rhn/kickstart/ks-rhel-s390x-server-5-u3/images/pxeboot/vmlinuz] Spacewalk cant create the distro in cobbler which makes this kickstart distribution: [ks-rhel-s390x-server-5-u3] unusable to Spacewalk. Version-Release number of selected component (if applicable): 530, 5/1 build How reproducible: Always Steps to Reproduce: 1. Sync s390x RHEL 5 Server and associated rhn-tools channels 2. Run a 'cobbler distro list' Actual results: s390x distros do not appear Expected results: s390x distros appear Additional info:
9b9949743b663a4f503347533d1d26aaaacf71bd
VERIFIED on 5/29 build.
1. I had a synced rhel-i386-server-5 channel. cobbler distro list returns actual distro listing (ks-rhel-i386-server-5*) 2. I synced rhel-s390x-server-5 channel. Immediately after the sync finished cobbler distro list doesn't return any new distros. Checking 15 minutes later - cobbler distro list returns also: ks-rhel-s390x-server-5-u2 ks-rhel-s390x-server-5-u3 ks-rhel-s390x-server-5-u4 Error message from #Description not found in the taskomatic log. Stage validated -> RELEASE_PENDING
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html