Red Hat Bugzilla – Bug 880936
[RFE] [ALL_LANG - SAM Web GUI] - Error handling Mechanism to be smarter and effective
Last modified: 2014-09-18 12:47:51 EDT
Created attachment 653345 [details]
Screen Shot for the error messages that showing in a new page.
Description of problem:
This is a strange problem I have observed. Suppose you - User-1, are logged in with Admin rights and with selecting a particular organization, at the time of login into SAM Web GUI.
Suppose, at the same time, there is somebody else - User-2, who are also logged in with Admin rights, opting some other organization at the time of login. Then User-2 deletes the Organization that User-1 is logged in with.
Now, if User-1 tries to go to the "Manage Organization" page from Administrator --> Manage Organization, he or she will get a Error page. This error has been referred with this bug as a Screen shot attached here above.
This may look like an abstract scenario to meet, but when it appears, the application should be able to manage and act according to the dynamic changes made in managing all data successfully in instant, without showing up these kind of error page.
Version-Release number of selected component (if applicable):
Subscription Asset Manager Version: 1.2.5-1h.el6_3
Steps to Reproduce:
1. Login as Admin in SAM Web GUI.
2. Select any Organization
1. On another system, Login as Admin in SAM Web GUI
2. Select any Organization other than that has been selected during Action
3. Now, Delete the Organization selected in Action-Phase-I
Administrator --> Manage Organization
Select the Organization of Action Phase-I from the list showing in the Left
pane of the window.
Now, go back to the first system
1. Click on Administrator --> Manage Organization
2. Observe the Result.
Some error page showing with AbstractController double rendering error.
The online app should handle this kind of error more efficiently, providing the current user more dynamic info regarding the parallel uses and management (adding, modifying, deleting org, or some other transactions) actions.
Additional info: Screen Shot attached.
You are absolutely correct. I have added this as an RFE to be addressed in future.
Moving to CFSE where the problem resides as well
I believe this is fixed with the new foreman base. I am closing this out as current release. If you disagree, please feel free to re-open