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.

Created attachment 1091759 [details]
all content view versions listing with invalid ID

Description of problem:
The URL parameters are not checked for validation if the ID really exists. Instead it sometimes continues to run on the all resources instead of a single resource item

Having an invalid ID can happen when you still have the UI open on that ID, but in an other session or through the API the Item is deleted.

Simple reproduction is to use a value of 9999

Example of content view versions with ID 9999 is attached in screenshot
/content_views/9999/versions



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


How reproducible:


Steps to Reproduce:
1. Use invalid ID (e.g. 9999) in the URLs
2.
3.

Actual results:
Unpredictable results, e.g. listing of all items

Expected results:
Failure that the identifier cannot be found


Additional info:

This is a duplicate of bug #1257586.

*** This bug has been marked as a duplicate of bug 1257586 ***