Bug 1377785

Summary: Host page shows Errata: Security errata applicable Content page shows no errata available
Product: Red Hat Satellite Reporter: ldomb
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.2CC: bbuckingham, bkearney, jsherril
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-27 17:16:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
securityerrataapplicable none

Description ldomb 2016-09-20 15:17:04 UTC
Created attachment 1202942 [details]
securityerrataapplicable

Description of problem:
When adding a host to Satellite 6.2.2 I see that there is errata available for the host. If I path the host via content page and apply all the pages the content page for the host says: 

Installable Errata
Security 0
Bug Fix 0
Enhancement 0

But the hosts page says:
Errata: Security errata applicable  


Version-Release number of selected component (if applicable):
6.2.2

How reproducible:


Steps to Reproduce:
1. Add a host via subscription-manager register --org="redhat" --activationkey="ak-Reg_To_Crash_soe_no_puppet" 
2. Go to the content page and apply patches until 0 are left
3. Go to the hosts page click on the host. In the Errata field you will see 
Security errata applicable even if there are none.

Actual results:
Errata field you will show 
Security errata applicable even if there are none.

Expected results:
No errata for this host

Additional info:

Comment 1 Brad Buckingham 2016-09-20 17:47:00 UTC
Justin, is the difference observed 'applicable' versus 'installable' errata?

Comment 2 Justin Sherrill 2016-09-20 20:33:54 UTC
Glancing at the code, I don't think so.  Both areas should only show installable.  Would need to setup and poke a reproducer to isolate the cause.

Comment 5 ldomb 2016-09-21 16:29:43 UTC
We can close this and here is why. 

The hosts page Errata shows the available errata within the overall content view not the actual content view version where the host is attached to. Therefor the state errata available is correct if the yum repos were synchronized and the host is not on the latest patch level in terms of yum repo sync. 

The content tab reflects the actual content view. 

Bug can be closed as its not a bug.

Comment 6 Bryan Kearney 2016-09-27 17:16:34 UTC
Closing based on comment 5.