Bug 1070386 - [RFE] Parameter overrides should provide dropdown menu of possible values
Summary: [RFE] Parameter overrides should provide dropdown menu of possible values
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: foreman
Version: 4.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: Installer
Assignee: Angus Thomas
QA Contact: Ami Jeain
URL: http://projects.theforeman.org/issues...
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 17:12 UTC by Dafna Ron
Modified: 2015-04-29 15:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-29 15:08:29 UTC
Target Upstream Version:


Attachments (Terms of Use)
screen shots (283.86 KB, application/x-gzip)
2014-02-26 17:12 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2014-02-26 17:12:04 UTC
Created attachment 868114 [details]
screen shots

Description of problem:

I'm installing a controller from foreman and when I override a value which is True we get a new field with the same Value. 
If we override a value (in this case True) we should not present the same value in the newly created parameter field. 

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

[root@dhcp163-108 ~]# rpm -qa |grep foreman
foreman-1.3.0.2-1.el6sat.noarch
openstack-foreman-installer-1.0.4-1.el6ost.noarch
foreman-selinux-1.3.0-1.el6sat.noarch
rubygem-foreman_api-0.1.6-1.el6sat.noarch
foreman-mysql-1.3.0.2-1.el6sat.noarch
foreman-mysql2-1.3.0.2-1.el6sat.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-5.el6ost.noarch
foreman-installer-1.3.0-1.el6sat.noarch
foreman-proxy-1.3.0-3.el6sat.noarch

How reproducible:

100%

Steps to Reproduce:
1. edit a host with foreman 
2. in parameter -> override the floating ip field
3.

Actual results:

a new created field is created but the "True" value is kept. 

Expected results:

1. if I override a value I think we can delete it from the field
2. this can be debated but I think we should either give the valid choices/examples in the empty field created or we should use the opposite value (so instead of True we should put False). 

Additional info:screen shots

Comment 3 Mike Burns 2015-04-29 15:08:29 UTC
This is a very minor issue in the context of staypuft and we're only fixing high priority issues.


Note You need to log in before you can comment on or make changes to this bug.