Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionOleksandr Shtaier
2016-01-14 09:41:11 UTC
Description of problem:
Trying to update content view information (content view id) for existing content view filter entity and constantly getting 404 error.
For example:
PUT: https://your_server/katello/api/v2/content_view_filters/16
{"content_view_id":100}
Error:
Received HTTP 404 response: {"displayMessage":"Couldn't find ContentViewFilter with id=16","errors":["Couldn't find ContentViewFilter with id=16"]}
Everything works fine in case I will try to update another field (e.g. 'type')
Version-Release number of selected component (if applicable):
6.1.6
How reproducible:
Always
Steps to Reproduce:
1. Create couple of content view entries
2. Create content view filter for one content view
3. Try to update content view filter and assign another content view for it
Actual results:
404 error is raised
Expected results:
Update procedure passed successfully
or
In case that scenario is wrong due any reasons corresponding documentation entries for API should be changed and proper error message should be generated and displayed
Additional info:
I do not believe this will be addressed in the next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.