Bug 1228278 - Incremental update displays errata counts but calls it Host count
Summary: Incremental update displays errata counts but calls it Host count
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard: rails-3.2.8
Depends On: 1240819
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-04 14:20 UTC by sthirugn@redhat.com
Modified: 2017-02-23 19:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 16:04:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Incremental update screenshot showing incorrect hosts (97.78 KB, image/png)
2015-06-04 14:20 UTC, sthirugn@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 11224 0 None None None 2016-04-22 16:31:26 UTC
Red Hat Bugzilla 1250678 0 unspecified CLOSED [RFE] Show both immediately affected hosts and all affected hosts in the Apply Errata page 2021-02-22 00:41:40 UTC

Internal Links: 1250678

Description sthirugn@redhat.com 2015-06-04 14:20:25 UTC
Created attachment 1034738 [details]
Incremental update screenshot showing incorrect hosts

Description of problem:
Incremental update displays errata counts but calls it Host count

Version-Release number of selected component (if applicable):
Sat 6.1 GA Snap 7

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Content -> Errata
2. Select multiple erratas and apply
3. Review the Apply Errata page

Actual results:
Number of errata is displayed under Host Count section

Expected results:
- Display the right number of affected content hosts

Additional info:

Comment 3 Walden Raines 2015-06-04 16:01:38 UTC
I cannot reproduce this following the steps given, is there anything else that needs to be done in order to reproduce this?

Comment 4 Og Maciel 2015-06-10 17:18:12 UTC
I spoke to Walden about this and we realized that this issue can only be truly verified once https://bugzilla.redhat.com/show_bug.cgi?id=1228292 is ON_QA

Comment 5 sthirugn@redhat.com 2015-06-16 14:19:02 UTC
Failed.  The Host count still shows the applicable errata count

Version tested: Sat 6.1 GA Snap 8

Comment 6 Walden Raines 2015-06-16 15:20:00 UTC
Well in that case I need some clear steps to reproduce as the ones in the description are not sufficient.  Something is missing.

Comment 8 Walden Raines 2015-06-16 19:31:07 UTC
Created redmine issue http://projects.theforeman.org/issues/10839 from this bug

Comment 9 Walden Raines 2015-06-17 15:56:57 UTC
(In reply to Walden Raines from comment #8)
> Created redmine issue http://projects.theforeman.org/issues/10839 from this
> bug

This issue is due to an older version of activerecord and is thus downstream only.

Comment 11 Walden Raines 2015-06-19 13:14:18 UTC
Merged downstream 400fe2b732a554fe0139aaa0856128882fa33add.

Comment 12 Bryan Kearney 2015-06-26 14:32:30 UTC
Delivered in Snap10

Comment 13 sthirugn@redhat.com 2015-07-07 20:33:10 UTC
Failed.  It looks like the fix for this is causing https://bugzilla.redhat.com/show_bug.cgi?id=1240819.  Unable to verify this bug for more one content host.

Comment 14 Walden Raines 2015-07-09 19:04:03 UTC
There is nothing to do here.  This can be verified once #1240819 is fixed.

Comment 16 Walden Raines 2015-07-27 21:37:43 UTC
Created redmine issue http://projects.theforeman.org/issues/11224 from this bug

Comment 17 Walden Raines 2015-07-27 22:46:39 UTC
PR: https://github.com/Katello/katello/pull/5377

Comment 19 sthirugn@redhat.com 2015-07-31 19:44:50 UTC
Test scenario 1:
1. I had three content hosts - all registered to the same content view.
2. Now I selected an applicable errata - click 'Apply Errata'
3. Select all three content hosts. Click 'Next'
4. Review the 'Apply Errata' page - Host Count showed 3.

Test scenario 2:
1. I had three content hosts - all registered to the same content view.
2. Now I selected an applicable errata - click 'Apply Errata'
3. Although three content hosts showed up as affected (since they all tied to the same content view) I selected one of those. Click 'Next'
4. Review the 'Apply Errata' page - Host Count showed 1.


My question:
What is Host Count actually mean? In the second scenario although I am trying to apply this errata on one content host - all content hosts will anyway get access to this errata since we are incrementally updating the content view which all of these content hosts subscribe.  Shouldn't be the affected host count be 3 instead of 1 in this case?

Comment 20 Mike McCune 2015-08-03 21:40:17 UTC
The Host Count is the # of hosts that will *immediately* get the errata installed upon completion of the incremental update process.

The other 2 you didn't select will not get the errata installed until you tell it to install it via the UI/API/CLI or an admin goes to a shell and runs 'yum update <package>'.

Just because Hosts have access to the errata does not mean that it is installed, this still requires a user action.

Comment 21 Walden Raines 2015-08-05 15:46:59 UTC
(In reply to sthirugn from comment #19)
> What is Host Count actually mean? In the second scenario although I am
> trying to apply this errata on one content host - all content hosts will
> anyway get access to this errata since we are incrementally updating the
> content view which all of these content hosts subscribe.  Shouldn't be the
> affected host count be 3 instead of 1 in this case?

Somewhat contrary to what Mike says above, I think that the intent here was to show the number of hosts affected by this action.

In scenario #2 above I would expect the count to display "3" since three content hosts will now have this errata available to them and would get it if they were to run a yum update.  It is true, however, that if you were to check the "apply" box that it would only apply the errata on the one selected host.

From what I can tell, the code, as written, would have never passed scenario #2 as it limits the count to the selected systems.

Good catch, will fix.

In addition, I will add some text to make the intent of the Content Host count clear.

Comment 22 sthirugn@redhat.com 2015-08-05 15:49:58 UTC
Failed in Sat 6.1 GA Snap 15 - as per Comment 19 and Comment 21.

Comment 23 sthirugn@redhat.com 2015-08-05 18:41:43 UTC
Currently the Host Count in question will just show the number of selected host counts.  Since this may not give a real picture of actual host count to the user, a new RFE https://bugzilla.redhat.com/show_bug.cgi?id=1250678 is written.  So I am marking this bug as VERIFIED in Sat 6.1 GA Snap 15.

Comment 24 Bryan Kearney 2015-08-12 16:04:16 UTC
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.


Note You need to log in before you can comment on or make changes to this bug.