Bug 698661

Summary:	Repo sync Job scheduler entries persist in the database even after the channel is deleted.
Product:	[Community] Spacewalk	Reporter:	ypismerov
Component:	Server	Assignee:	Tomas Lestach <tlestach>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.3	CC:	clasohm
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:	2011-09-30 11:41:19 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:	723481

Description ypismerov 2011-04-21 13:39:24 UTC

Description of problem:


Repository sync scheduled tasks persist even after the channel is removed.
This causes email notifications like this:

<quote>

Taskomatic bunch repo-sync-bunch was scheduled to run within the repo-sync-1-102 schedule.

Subtask repo-sync failed.

For more information check /var/lib/rhn/tasko/org1/repo-sync-bunch/repo-sync_733367_err.

</quote>




root@spacewalk rhn]# less  /var/lib/rhn/tasko/org1/repo-sync-bunch/repo-sync_733367_err
2011-04-21 03:21:07,912 [DefaultQuartzScheduler_Worker-8] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  - No such channel with channel_id 102
2011-04-21 03:21:07,913 [DefaultQuartzScheduler_Worker-8] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask  -




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


Spacewalk v1.3


How reproducible:



Steps to Reproduce:
1. Set up repository sync schedule in a given channel.
2. Delete the channel.
3. Wait for the next run of the scheduled job. 
4. Check /var/log/rhn/taskomatic_daemon.log and look for an error similar to the following:

INFO   | jvm 1    | 2011/04/21 03:21:07 | 2011-04-21 03:21:07,912 [DefaultQuartzScheduler_Worker-8] ERROR com.redhat.rhn.taskomatic.task.RepoSyncTask - No such channel with channel_id 102

  
Actual results:


Expected results:


Additional info:


Manual removing the specific row from QRTZ_CRON_TRIGGERS fixes the problem.

Comment 1 Jan Pazdziora 2011-07-20 11:52:46 UTC

Aligning under space16.

Comment 2 Tomas Lestach 2011-09-30 11:41:19 UTC

I remember I fixed that already.

spacewalk.git: 47043db7583f648f279929285f8a6ee8f85c470f

The fix is present already in spacewalk-java-1.3.48

Closing as CURRENTRELEASE.