Bug 1855041

Summary: Label inside Security Policy spoke is not upper case
Product: Red Hat Enterprise Linux 8 Reporter: Jan Stodola <jstodola>
Component: oscap-anaconda-addonAssignee: Matěj Týč <matyc>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: medium    
Version: 8.3CC: mhaicman, pzatko, wsato
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 03:46:16 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:
Bug Depends On:    
Bug Blocks: 1812825    
Attachments:
Description Flags
Screenshot none

Description Jan Stodola 2020-07-08 18:12:12 UTC
Created attachment 1700341 [details]
Screenshot

Description of problem:
The name of the spoke displayed in the Security Policy spoke changed from "SECURITY POLICY" to "Security Policy". See the attached screenshot.

This spoke is the only spoke in anaconda not having the label in the spoke printed with all upper case letters.

Version-Release number of selected component (if applicable):
RHEL-8.3.0-20200701.2
anaconda-33.16.3.10-1.el8
oscap-anaconda-addon-1.1.1-3.el8

How reproducible:
Always

Steps to Reproduce:
1. Start graphical installation.
2. Proceed to the "Security Policy" spoke.
3. Check the label in the top left screen.

Actual results:
"Security Policy"

Expected results:
All letters upper case, like in the rest of anaconda spokes:
"SECURITY POLICY"

Comment 9 errata-xmlrpc 2020-11-04 03:46:16 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 (oscap-anaconda-addon bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2020:4772