Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1145314

Summary: Do we need to expose facter in our field descriptions?
Product: Red Hat OpenStack Reporter: Matt Reid <mreid>
Component: foremanAssignee: Dominic Cleal <dcleal>
Status: CLOSED NOTABUG QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 6)CC: mburns, rhos-maint, yeylon
Target Milestone: ---Keywords: UserExperience, ZStream
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-23 11:53:19 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
First three fields all talk about getting values from facter none

Description Matt Reid 2014-09-22 19:56:55 UTC 
Description of problem:
When creating an Operating System entry, several fields mention facter, as a non-Puppet expert (I've heard it relates to Puppet), I have no idea what that means, and thought it was a typo. If we're specifying values, should the field description make it sound like that value will get pulled from something? If these values are specifying information that will be pushed into, or available from facter, perhaps the text should be updated to make it sound less like these values will be populated from facter.

Name
OS name from facter; e.g. RedHat

Major version
OS major version from facter; e.g. 6

Minor version
OS minor version from facter; e.g. 5


Version-Release number of selected component (if applicable):
foreman-installer-1.5.0-0.6.RC2.el6ost.noarch
rhel-osp-installer-0.1.10-2.el6ost.noarch
openstack-foreman-installer-2.0.20-1.el6ost.noarch
ruby193-rubygem-staypuft-0.2.5-1.el6ost.noarch

Additional info:
Comment 1 Matt Reid 2014-09-22 19:58:07 UTC 
Created attachment 940156 [details]
First three fields all talk about getting values from facter
Comment 4 Dominic Cleal 2014-09-23 11:53:19 UTC 
These fields contain data pulled from facter, seems accurate enough to me.
Comment 5 Matt Reid 2014-09-23 13:22:36 UTC 
If the new Operating System dialog is a dialog where the user has to enter all of these values, how are they getting pulled from facter? At this point they're user generated values, no? I don't see any buttons on the dialog that will pull data from somewhere and populate values for me.

Maybe if you're editing an operating system config that was pulled from somewhere, those descriptions are accurate, but it seems like at least during creation, they aren't.