Hide Forgot
Description of problem: Can't create config group via API, receiving 500 response with `ActiveModel::ForbiddenAttributesError` message. Version-Release number of selected component (if applicable): satellite-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Try to create config group via API (path api/v2/config_groups , request body can contain name only, e.g. {"name": "AAecyofVVk"}) 2. 3. Actual results: 2016-09-21 14:12:31 - nailgun.client - DEBUG - Making HTTP POST request to https://*hostname*/api/v2/config_groups with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}} and data {"name": "AAecyofVVk"}. 2016-09-21 14:12:32 - nailgun.client - WARNING - Received HTTP 500 response: { "error": {"message":"ActiveModel::ForbiddenAttributesError"} } Expected results: Config group was successfully created Additional info:
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16681 has been resolved.
VERIFIED in Sat 6.3.0 Snap 4 In [1]: nailgun.entities.ConfigGroup().create() 2016-10-19 13:39:48 - nailgun.client - DEBUG - Making HTTP POST request to https://hostname.redhat.com/api/v2/config_groups with options {'verify': False, 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}} and data {"name": "fwtmdI"}. 2016-10-19 13:39:49 - nailgun.client - DEBUG - Received HTTP 201 response: {"created_at":"2016-10-19 10:39:49 UTC","updated_at":"2016-10-19 10:39:49 UTC","id":2,"name":"fwtmdI","puppetclasses":[]} Out[1]: nailgun.entities.ConfigGroup(nailgun.config.ServerConfig(url='https://hostname.redhat.com', verify=False, auth=('admin', 'changeme')), id=2, name=u'fwtmdI')
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/RHSA-2018:0336