Description of problem: Incremental update on more than one content host fails Version-Release number of selected component (if applicable): Sat 6.1 GA Snap 11 How reproducible: Always Steps to Reproduce: 1. Navigate to Content -> Errata 2. Select any one (or more) of the applicable erratas. Click 'Apply Errata' 3. Select more than one content host (Note: The errata should be applicable to the content hosts which means incremental update should be triggered). Click 'Next' Actual results: The page where the Content view version update would be suggested is not shown (see screenshot) Expected results: The page where the Content view version update would be suggested is shown Additional info: I also noticed error in production.og (attached in bugzilla)
Created attachment 1049564 [details] production.log
Created attachment 1049565 [details] screenshot_actual
Created attachment 1049566 [details] screenshot_expected
Created redmine issue http://projects.theforeman.org/issues/11075 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/11075 has been closed ------------- Walden Raines Applied in changeset commit:katello|5bfc23ddf157d8cf55dd793c62a329043e87e9ed.
Digging into this one. I have two systems that can consume available package updates - a "yum update" shows me packages that correspond to existing errata in my repo. Yet the Content Hosts UI shows me zero applicable errata for the systems; likewise, the Apply Errata page tells me there are zero systems for which the errata can apply. This is with RHEL5, if it matters.
Figured out the issue above. Initial report implied this was regarding incremental updates but didn't specifically mention anything about how to set them up. Good to go now. QE Verified in Snap 14. Applied 3 errata across two systems; got the notification about adding it to a content view; installs were successful.
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.