Bug 1250678 - [RFE] Show both immediately affected hosts and all affected hosts in the Apply Errata page
Summary: [RFE] Show both immediately affected hosts and all affected hosts in the Appl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Errata Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-05 18:38 UTC by sthirugn@redhat.com
Modified: 2018-09-04 19:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:23:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Host count in Apply Errata page (118.94 KB, image/png)
2015-08-05 18:38 UTC, sthirugn@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1228278 0 unspecified CLOSED Incremental update displays errata counts but calls it Host count 2021-02-22 00:41:40 UTC

Internal Links: 1228278

Description sthirugn@redhat.com 2015-08-05 18:38:36 UTC
Created attachment 1059599 [details]
Host count in Apply Errata page

Description of problem:
[RFE] Show both immediately affected hosts and all affected hosts in the Apply Errata page

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

How reproducible:
N/A

Steps to Reproduce:
1. Register/subscribe three content hosts to satellite - all registered to the same content view.
2. Select an applicable errata - click 'Apply Errata'
3. Although three content hosts show up as affected (since they all tied to the same content view) select only one of those. Click 'Next'
4. Review the 'Apply Errata' page - Host Count showed 1.

Actual results:
- Host count currently shows the content hosts I selected in the previous page.
- Aalthough I try to apply the errata on one content host - all content hosts will anyway get access to this errata since it triggers the incremental update of the content view to which all of these content hosts subscribe.

Expected results:
A more logical way to solve this is by 
1. Remove 'Host Count' column
2. Add 'Two new columns' 
 - 'Hosts immediately affected'
 - 'Total Affected Hosts'
3. At the time of rendering of this page, 'Apply Errata to Content Hosts immediately after publishing' checkbox will be unchecked. So
 - 'Hosts immediately affected' should be displayed zero when the page displays
 - If user checks this check box - then 'Hosts immediately affected' should be populated with the current selected hosts
 - If the user toggles between checking/unchecking box - the 'Hosts immediately affected' should toggle between current selected hosts and zero.
4. 'Total Affected Hosts' should always show the number of hosts subscribed to the content view which is being incrementally updated.


Additional info:

Comment 1 Bryan Kearney 2016-07-08 20:22:58 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 4 Roxanne Hoover 2018-04-26 19:39:19 UTC
At a high-level, it seems like the problem is that it is not clear to the user how many hosts out of total affected hosts are getting the errata applied to it and which hosts are affected immediately, since the Host Count column is based on the hosts you've selected and not of the previous totals mentioned.

The proposed solution makes sense.

Comment 5 sthirugn@redhat.com 2018-06-14 18:12:10 UTC
Thinking about this bug after three years of writing it:

My earlier proposed solution would be too complicated to implement.  I think maybe we can just show a warning notification in the UI that although you are trying to apply the updates to the specific hosts, all the hosts subscribed to this content view will have access to the updated content. This is all is really needed.

Comment 6 Bryan Kearney 2018-09-04 19:23:12 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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