Bug 603227 - 500 Internal Server Error when trying to view list of applicable systems for an errata via SSM
Summary: 500 Internal Server Error when trying to view list of applicable systems for ...
Keywords:
Status: CLOSED DUPLICATE of bug 599742
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: rhn522
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-11 23:39 UTC by Xixi
Modified: 2010-06-14 22:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-14 22:04:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Xixi 2010-06-11 23:39:15 UTC
Description of problem:
When working with a group, and under SSM->Errata then trying to view the systems on which the errata is applicable, it throws 500 Internal Server Error.
But if you go to the errata tab and click on the number, it does show the systems on which the errata is applicable.

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

How reproducible:
Always.

Steps to Reproduce:
1. Login to RHN Hosted (rhn.redhat.com), click Systems
2. In the grey box, click System Groups
3. Pick a group and click the Use Group button (you need to have made a group already).
4. Under System Set Manager, click the Errata tab.
5. One of the columns will be "Systems".  Click on any of the numbers in that column to try to view the systems affected by that errata.
  
Actual results:
The link goes to https://rhn.redhat.com/network/systems/ssm/errata/systems_affected.pxt?eid=9966 which returns Internal Server Error

Expected results:
Page displays correctly. No internal server error.

Additional info:
For Satellite 5.3, /network/systems/ssm/errata/systems_affected.pxt?eid=xyz renders fine.

Comment 1 Grant Gainey 2010-06-14 22:04:24 UTC

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


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