Bug 766587 - Cannot access "Probe Status" page (Status 500 Error ISE)
Summary: Cannot access "Probe Status" page (Status 500 Error ISE)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 1.6
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space17
TreeView+ depends on / blocked
 
Reported: 2011-12-12 11:35 UTC by Lukas Pramuk
Modified: 2012-01-18 11:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-18 11:24:05 UTC


Attachments (Terms of Use)
traceback (1.15 KB, text/plain)
2011-12-12 11:46 UTC, Lukas Pramuk
no flags Details

Description Lukas Pramuk 2011-12-12 11:35:41 UTC
Description of problem:
I cant access Probe Status page. Instead i get Status 500 Error

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

How reproducible:
100% on PostgreSQL

Steps to Reproduce:
1. login to your Spacewalk
2. navigate to Systems -> System Group -> choose a grp -> Probes
3. and you get 500 Error 
  
Actual results:
clicking on "Probes" shows "500 Error - Internal Server Error"
page

Expected results:
clicking on "Probes" shows "Probe Status" page

Additional info:
pgSQL related

Comment 1 Lukas Pramuk 2011-12-12 11:46:13 UTC
Created attachment 545675 [details]
traceback

Comment 2 Jan Pazdziora 2011-12-12 14:51:43 UTC
What version of spacewalk-pxt do you use? 'cause this should have been fixed in spacewalk-web-1.6.34-1.

Comment 3 Lukas Pramuk 2012-01-18 11:13:48 UTC
Apparently this has been fixed. I'm not able to reproduce the bug on spacewalk-nightly. Still needinfo?

Comment 4 Jan Pazdziora 2012-01-18 11:24:05 UTC
(In reply to comment #3)
> Apparently this has been fixed. I'm not able to reproduce the bug on
> spacewalk-nightly. Still needinfo?

Let's close as CURRENTRELEASE then.


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