Bug 701798 - removal of a channel which had scheduled sync of attached repo(s) keeps taskomatic bunch in place
Summary: removal of a channel which had scheduled sync of attached repo(s) keeps tasko...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 540
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-05-03 21:47 UTC by Jan Hutař
Modified: 2014-07-04 13:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:28:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Hutař 2011-05-03 21:47:39 UTC
Description of problem:
When you have yum repo attached to the channel and have regular synces scheduled and uses spacewalk-remove-channel to remove the channel, taskomatic bunch for syncing the channel survives (and probably produces some errors as well).


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



How reproducible:
always


Steps to Reproduce:
1. Create channel and repository
   Channels -> Manage Software Channels -> create new channel
   Channels -> Manage Software Channels -> Manage Repositories -> create new repository
2. Attach the repository to the channel
   Channels -> Manage Software Channels -> <your channel> -> Repositories -> Add / Remove
3. Schedule daily sync
   Channels -> Manage Software Channels -> <your channel> -> Repositories -> Sync
4. Using API call ensure we have active bunch for that:
   client.taskomatic.org.listActiveSchedules(key)
   data_map = {'channel_id': '103'}; cron_expr = 0 20 8 ? * *; active_from = 20110503T08:12:19; bunch = repo-sync-bunch; id = 16; job_label = repo-sync-1-103;
5. # spacewalk-remove-channel -c <your channel>
6. Use API call as in "4." to ensure bunch dissipated


Actual results:
In "6." same bunch is still there.


Expected results:
In "6." bunch from "4." should not be present.


Additional info:
Found during testing bug 663326.


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