Description of problem: When syncing repo to a channel, errata cache doesn't get updated for the affected channel. Version-Release number of selected component (if applicable): sat540 How reproducible: always Steps to Reproduce: 1. create a custom channel and subscribe a server to that channel 2. associate a repository to the channel and sync it (the repo shall contain at least one package update for the server) 3. wait until channel repodata is generated and at least 10 minutes to let the errata cache to get regenerated 4. check WebUI to see package updates Actual results: No package updates Expected results: All possible package updates displayed Additional info: spacewalk-repo-sync shall trigger a ErrataCacheTask into the taskomatic queue when it has modified channel content (by inserting update_errata_cache_by_channel into the rhnTaskQueue).
Taking.
spacewalk.git master: 37efecb997ef90a71269fc6594f02ff9eb6c1f6e
cherry-picked to satellite.git as commit ef45b621d4989c7f2246e023dfacffe4165035a4
Moving to Verified: Testing procedure: - After the reposync updates are shown on webui - Client is able to fetch packages right after, repodata regeneration - When multiple channels assigned to a repository, errata cache is regenerated only for appropriate channel Verified against: spacewalk-backend-1.2.13-23.el5sat
Please be so kind and add a few key words to the Technical Note field of this bugzilla entry using the following structure: Cause: Consequence: Fix: Result: For details, see: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Consequence: Fix: Result:
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,7 @@ -Cause: +Cause: Running spacewalk-repo-sync did not automatically trigger yum repodata rebuild. -Consequence: +Consequence: yum repodata was not rebuilt after running spacewalk-repo-sync. -Fix: +Fix: Running spacewalk-repo-sync now automatically triggers repodata rebuild. -Result:+Result: The results are astonishing.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,7 @@ -Cause: Running spacewalk-repo-sync did not automatically trigger yum repodata rebuild. +Cause: Running spacewalk-repo-sync did not automatically trigger errata cache rebuild. -Consequence: yum repodata was not rebuilt after running spacewalk-repo-sync. +Consequence: applicable package updates were not visible. -Fix: Running spacewalk-repo-sync now automatically triggers repodata rebuild. +Fix: Running spacewalk-repo-sync now automatically triggers errata cache rebuild. Result: The results are astonishing.
Milan, many thanks for the excellent CCFR.
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/RHBA-2011-0190.html
*** Bug 654398 has been marked as a duplicate of this bug. ***