Bug 1194900

Summary: Can we change "Parametrized_Classes_in_ENC" to say "Parameterized"...
Product: Red Hat Satellite Reporter: Matt Reid <mreid>
Component: SettingsAssignee: Ohad Levy <ohadlevy>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.6CC: bkearney, cwelton, rohoover, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/11645
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 20:54:57 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:
Attachments:
Description Flags
Parametrized none

Description Matt Reid 2015-02-20 21:43:12 UTC 
Description of problem:
I'm not sure if this is something we're pulling from elsewhere, or if we named it this, but "Parametrized_Classes_in_ENC" shows in the Puppet table in Settings. 

The more common spelling for that is Parameterized, as far as I know.

Version-Release number of selected component (if applicable):
6.0.6
Comment 1 Matt Reid 2015-02-20 21:43:52 UTC 
Created attachment 994062 [details]
Parametrized
Comment 2 RHEL Program Management 2015-02-21 06:24:32 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 4 Bryan Kearney 2015-09-01 17:45:32 UTC 
Created redmine issue http://projects.theforeman.org/issues/11645 from this bug
Comment 5 Bryan Kearney 2015-09-02 10:03:07 UTC 
Upstream bug component is Provisioning
Comment 6 Bryan Kearney 2015-09-02 17:24:49 UTC 
Upstream bug component is Settings
Comment 7 Ohad Levy 2016-03-06 09:42:11 UTC 
UI part has changed in http://projects.theforeman.org/issues/7167
Comment 8 Bryan Kearney 2017-01-04 20:54:57 UTC 
This is an older bug, which is being tracked upstream. We will not be tracking this downstream. When the upstream issue is resolved, the next rebase will pull in the fix.