Bug 1070389

Summary:	foreman: unable to delete a field if we override a value on host edit
Product:	Red Hat OpenStack	Reporter:	Dafna Ron <dron>
Component:	foreman	Assignee:	Mike Burns <mburns>
Status:	CLOSED ERRATA	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	dcleal, mburns, mlopes, ohochman, rhos-maint, sgordon, yeylon
Target Milestone:	ga
Target Release:	Installer
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-21 18:03:59 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:

Description Dafna Ron 2014-02-26 17:16:29 UTC

Description of problem:

when I edit a host and override a value a new field is created 
if I changed my mind at some point I either have to discard all the changes or fill in manually the same value I overridden. 

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

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 -> parameter
2. override a value
3. a new field is created 
4. try to delete the field. 

Actual results:

once we override we cannot remove the field 

Expected results:

we should be able to remove the field and go back to the default value. 

Additional info:

Comment 1 Dominic Cleal 2014-02-27 09:35:25 UTC

Cannot reproduce on upstream Foreman 1.4, so should be fine in RHOS 5.

Comment 6 Ami Jeain 2014-08-07 12:50:52 UTC

verified in staypuft. no such symptom

Comment 8 errata-xmlrpc 2014-08-21 18:03:59 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.

http://rhn.redhat.com/errata/RHBA-2014-1090.html