Description of problem: It seems that package profile sync has in 530 a lot of problems. 1. When syncing package profiles and packages from the original profile are not accessible for the specified system, there;re listed as missing packages. If we want to list the next part of missing packages using ">", getting an ISE. 2. Next problems are listed in the "Additional info" section. Version-Release number of selected component (if applicable): Sat530 How reproducible: always Steps to Reproduce: 1. pick up 2 systems each registered to a different base channel (f.e. RHEL and Fedora) 2. Navigate to <system_to_be_synced> - Software - Profiles, select <compare_to_system>, hit Compare 3. Click "Select All" and continue by pressing "Sync packages to <compare_to_system>" 4. "Schedule Sync" 5. Make sure you were redirected to systems/details/packages/profiles/MissingPackages.do?... are there are more missing packages than actually displayed. 6. Press ">" to see the next part of missing packages. Actual results: ISE Expected results: Syncing profiles working properly. Additional info: 1. Note that the same happens when creating a profile and syncing system to the selected profile. 2. Note that there are other issues, that do not work during the sync wizard - if picking a date for sync schedule, sync will be scheduled ASAP anyway - if pressing either "Remove listed packages from sync" or "Subscribe to channels if available" on the MissingPackages.do, no event will be scheduled with message "There are no packages to sync." even if there were plenty of package to sync. 3. First part of this bug is similar to BZ#559551.
Issues from description fixed. spacewalk.git: 84d12a3dd96d67b38e8b30465673a404fa0e33cc For QA: Please test the whole package sync process very carefully, because it was significantly rewritten.
satellite.git: 44fd713bfdf10228660dbc5787c9fa1e0b1f55af
One more commit, that fixes system/profile sync ... spacewalk.git: f4d30229c16b1ad5af1e1606ec1efce4fbcb800e satellite.git: 7e68ae9a16a1a5c97cb34324e39e6fd6f24bbeda (actually fix for BZ#576907) fix available in spacewalk-java-0.5.44-74-sat
Taking QA contact for the bug verification.
Changing to verified: Testing procedure: Running various use cases and seeing rhn_check -vv on targeted system. With OLD set of packages: 1) Compare to System, seeing next page of selected packages result: FAIL, ISE 2) Compare to Stored profile, seeing next page of selected packages result: Ok, next page loaded 3) Finnished syncing with Compare to System result: Ok, system synced properly 4) Finnished syncing with Compare to Stored profile result: Ok, system synced 5) Picking up a date for sync schedule (Stored profile) result: FAIL, sync sheduled ASAP 6) "Subscribe to channels if available" result: FAIL, no event has been scheduled with message "There are no packages to sync." but there were plenty of package to sync." 7) Remove listed packages from sync result: FAIL, "There are no packages to sync." With NEW errata packages: 1) Compare to System, seeing next page of selected packages result: Ok, next page loaded 2) Compare to Stored profile, seeing next page of selected packages result: Ok, next page loaded 3) Finnished syncing with Compare to System result: Ok, system synced 4) Finnished syncing with Compare to Stored profile result: Ok, system synced properly 5) Picking up a date for sync schedule (Stored profile) result: Ok, sync scheduled, system synced about 2 minutes after specified date 6) "Subscribe to channels if available" result: Ok, rest of packages synced properly 7) Remove listed packages from sync result: Ok, rest of packages synced properly Configuration: Satellite: rhel-i386-server-5, Sat530 Target system: rhel-i386-server-5, with enabled provisioning Profile system: rhel-i386-server-5 Verified against: (on rhel-i386-server-5) python-cheetah-2.0.1-1 cobbler-1.6.6-5 spacewalk-web-0.5.23-34 spacewalk-java-0.5.44-74 spacewalk-backend-0.5.28-40.x.2
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-2010-0369.html
*** Bug 562722 has been marked as a duplicate of this bug. ***