Bug 766587

Summary: Cannot access "Probe Status" page (Status 500 Error ISE)
Product: [Community] Spacewalk Reporter: Lukas Pramuk <lpramuk>
Component: WebUIAssignee: Jan Pazdziora <jpazdziora>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.6CC: jpazdziora, slukasik
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-18 11:24:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 765736    
Attachments:
Description Flags
traceback none

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.