Bug 1271009

Summary:	Scheduled items return Internal Server Error
Product:	[Community] Spacewalk	Reporter:	max
Component:	WebUI	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.4	CC:	jdobes
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-21 13:12:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description max 2015-10-12 22:21:39 UTC

Description of problem:
Attempts to view any items in the Scheduled category return an Internal Server Error

Version-Release number of selected component (if applicable):
Spacewalk 2.4 on Fedora 22, x86_64

How reproducible:
Persists between fresh installs

Steps to Reproduce:
1. Schedule a job (such as pushing updates)
2. Select the job in the Schedule view (regardless of job status)

Actual results:
Internal Server Error is returned

Expected results:
Details of the scheduled item

Additional info:

Comment 1 Jan Dobes 2015-10-15 16:57:08 UTC

Seems that restarting Spacewalk fixes the ISE for me. But it would be good to find problem in the code.

Comment 2 max 2015-10-16 04:58:30 UTC

Intriguing! I kicked it with a restart as well (via the UI and not system restart) and that seems to have fixed that issue (for now at least). Very odd though.

Comment 3 max 2016-04-24 17:11:11 UTC

Did a fresh reinstall on Fedora 22 Server as per https://fedorahosted.org/spacewalk/wiki/HowToInstall with the embedded database. Issue still occurs until Spacewalk is restarted via GUI. On system restart / CLI restart the issue recurs.

Comment 4 max 2016-09-05 19:40:49 UTC

Following official instructions this also appears on Fedora 23. This issue does now appear to show using CentOS 7 however.

Comment 5 max 2016-09-05 19:41:36 UTC

Apologies for forgetting this also applies to Spacewalk 2.5.

Comment 6 Michael Mráka 2019-10-21 13:12:09 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.