Bug 1688636

Summary: Missing checkbox to toggle between applicable errata and installabe errata in the errata content hosts page.
Product: Red Hat Satellite 6 Reporter: Hao Chang Yu <hyu>
Component: Hosts - ContentAssignee: Hao Chang Yu <hyu>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: zhunting
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: tfm-rubygem-katello- Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:40:29 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:
Description Flags
All Errata none

Description Hao Chang Yu 2019-03-14 06:52:17 UTC
Description of problem:

The checkbox to toggle between applicable errata and installabe errata in the errata content hosts page is missing because of the following typo in the html template.


&lt;div class="filters"&gt;    <=========== Class should be replaced with "data-block" 
    &lt;label class="checkbox-inline"&gt;
      &lt;input type="checkbox" ng-model="restrictInstallable" ng-change="toggleInstallable()"/&gt;
      &lt;span translate&gt;Only show content hosts where the errata is currently installable in the host's Lifecycle Environment.&lt;/span&gt;

Comment 3 Bryan Kearney 2019-03-25 22:05:03 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26353 has been resolved.

Comment 6 Stephen Wadeley 2019-04-01 17:02:10 UTC
Created attachment 1550684 [details]

Comment 7 Stephen Wadeley 2019-04-01 17:02:41 UTC
Created attachment 1550685 [details]

Comment 8 Stephen Wadeley 2019-04-01 17:03:13 UTC
Created attachment 1550686 [details]
All Errata

Comment 11 errata-xmlrpc 2019-05-14 12:40:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.