Red Hat Bugzilla – Bug 1001922
on pxt page there is an incorrect menu displayed causing ISE
Last modified: 2015-01-13 04:45:30 EST
Description of problem:
With special sequence of clicking on webUI and using back button of your browser or editing URL, you can confuse pxt pages so they display different menu for the page causing not enough parameters in the links causing ISE.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have system with provisioning entitlement and ID 1000010020 and some
2. In webUI go to our starting point: its overview page
Systems -> <your_system> -> Details -> Overview
3. Go to some snapshot info page which is a pxt page:
Provisioning -> Snapshots -> <some_snapshot> -> Packages
4. Press "Back" button 4 times so you are back on Overview page
5. Click to: Schedule System Reboot
6. Note same menu as when you were in the step "3." is displayed
7. Click on Packages menu item which is:
(note the missing "ss_id" param in the URI)
ISE on webUI.
In error_log there is:
[Wed Aug 28 02:47:43 2013] [error] Execution of /var/www/html/network/systems/details/history/snapshots/packages.pxt failed at Wed Aug 28 02:47:43 2013: no snapshot_id at /usr/share/perl5/vendor_perl/Sniglets/Snapshot.pm line 70.
[Wed Aug 28 02:47:43 2013] [error] Traceback sent to root@localhost at /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm line 563.
Correct menu displayed, so no ISE possible.
I was not able to reproduce on a fresh browser (Firefox), I have seen this on mine (Opera) after a while of clicking around.
IMO not a sat560 blocking issue.
Right, setting correct menu for the reboot_confirm.pxt page ...
Looks like this page have same issue, but it is probably common to all pxt pages:
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state.
The Satellite 5.7 GA Errata:
Satellite 5.7 Release Notes:
Satellite Customer Portal Blog announcement for release:
NOTE: This specific bug did not get verified and being closed as assumed fixed. Please reopen if this is not resolved within the release.