Description of problem:
Creating a 'new host' fails for lifecycle_env and content_view saying "can't be blank", even though these values were set.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a "new host"
2. Provide "life-cycle env" and "content-view" values and also all the other needed values.
3. Click submit button.
To get a message "can't be blank" for "lifecycle-env" and "content-view".
"New host" page submission should be successful.
workaround: Again provide the values of "lifecycle-env" and "content-view".
*** Bug 1317071 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/14166 from this bug
Being handled here -> https://github.com/theforeman/foreman/pull/3309
Upstream bug component is Provisioning
Moving to POST since upstream bug http://projects.theforeman.org/issues/14166 has been closed
The title is more of a symptom, but the root cause for this bug is this line in the upstream foreman.
def register_facet_relation(klass, facet_config)
has_one facet_config.name, :class_name => facet_config.model.name, :foreign_key => :host_id, :inverse_of => :host
accepts_nested_attributes_for facet_config.name, :update_only => true
Basically accepts_nested_attributes_for usage does not provide an easy way to include in a form without sending blank attributes
Applied in changeset commit:5d64eef2cba8e56ad39510c3bd1d724bd52762eb.
VERIFIED with sat62-snap6
This issue is not seen anymore with latest snaps.
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.