Bug 1004991 - Refreshing browser on "System Default Custom Info" page causes "row:Not Found" error
Refreshing browser on "System Default Custom Info" page causes "row:Not Found...
Product: Subscription Asset Manager
Classification: Red Hat
Component: katello (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: rc
: ---
Assigned To: Katello Bug Bin
Depends On:
Blocks: sam20-tracker
  Show dependency treegraph
Reported: 2013-09-05 20:25 EDT by bmorriso
Modified: 2017-06-26 16:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-06-26 16:33:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bmorriso 2013-09-05 20:25:59 EDT
Description of problem:
On the organizations admin page, after selecting an org and navigating to the Sytem Default Custom Info sub-page, refreshing the page causes the error "There was an error retrieving that row:Not Found" to appear in the top of the right pane. This error persists regardless of which org you select. 

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

How reproducible:

Steps to Reproduce:
1. navigate to organizations page.
2. select any organization.
3. navigate to that organization's "System Default Custom Info" page.
4. refresh the browser.
5. click any other organization.

Actual results:
"There was an error retrieving that row:Not Found" appears in the header of the right pane.

Expected results:
The selected org's "Details Page" would appear. 

Additional info:
Comment 1 Bryan Kearney 2017-06-26 16:33:34 EDT
The release of Satellite 5.8 we are deprecating the support of Subscription Asset Manager. The release notes for 5.8 can be found at https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/pdf/release_notes/Red_Hat_Satellite-5.8-Release_Notes-en-US.pdf.

I am therefore closing out this bug as WONTFIX. If you believe this to be an error, please feel free tor each out to either Rich Jerrido or Bryan Kearney. Thank you!

Note You need to log in before you can comment on or make changes to this bug.