Instead of requiring an update to a host's facet attributes to include the ID of the facet, look up the needed ID in the API controller and add to params. Facet IDs are not, imho, a user-facing aspect that needs to be exposed. <pre> { host_id: 123, host: { name: "abc.example.com", content_facet_attributes: { id: 1234, <---- REMOVE lifecycle_environment_id: 12, content_view_id: 12 }, subscription_facet_attributes: { id: 1234, <---- REMOVE service_level: "Premium" } } } </pre>
Created from redmine issue http://projects.theforeman.org/issues/13849
Upstream bug assigned to sshtein
Moving to POST since upstream bug http://projects.theforeman.org/issues/13849 has been closed ------------- Shimon Shtein Applied in changeset commit:ec76b0092f9af5b8f7e2e02777f376b6b6e0d711.
Verified in Satellite 6.2 Beta Snap 6 Compose 1. Behavior now is as expected.
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. https://access.redhat.com/errata/RHBA-2016:1500