Bug 1415005

Summary: Empty Columns inside Content -> Errata -> Apply
Product: Red Hat Satellite Reporter: Craig Donnelly <cdonnell>
Component: WebUIAssignee: satellite6-bugs <satellite6-bugs>
WebUI sub component: Katello QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: bbuckingham, kdixon
Version: 6.2.6   
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: 2017-01-20 15:23:40 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:
Embargoed:

Description Craig Donnelly 2017-01-19 23:34:50 UTC 
Description of problem:
Under the Content -> Errata page, if you choose some errata and click the 'Apply' button, this will take you to a screen to choose hosts to apply the errata to.

On this screen, there are some columns of information that are blank for all hosts, that should /never/ be blank. (Environment and Content View)

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

How reproducible: 100%

Steps to Reproduce:
1. Click Content -> Errata
2. Check some errata, click apply.
3. Observe Environment / Content View columns for content hosts.

Actual results:
No content in these columns for any hosts.

Expected results:
Should list current Environment / Content View.

Additional info:
This may be causing an additional issue with the Dropdown box on this page to select hosts only in a particular 'lifecycle environment' not taking effect / working at all. I will file a separate BZ for this.
Comment 2 Kathryn Dixon 2017-01-19 23:43:06 UTC 
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/host-configuration-guide/chapter-3-viewing-and-applying-errata

Following this guide you can 100% reproduce this.
Comment 4 Brad Buckingham 2017-01-20 15:23:40 UTC 

*** This bug has been marked as a duplicate of bug 1371406 ***