Bug 701899

Summary: when spacewalk-repo-sync is running for a given channel, I can delete it through WebUI
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 540   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-04 13:27:46 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: 462714    

Description Jan Hutař 2011-05-04 08:44:05 UTC 
Description of problem:
When spacewalk-repo-sync is running for a given channel, I can delete it through WebUI. This is inconsistent with the fact, spacewalk-remove-channel throws an error and denies to continue.


Version-Release number of selected component (if applicable):
Sat 5.4.1:
  spacewalk-backend-tools-1.2.13-48.el6sat.noarch
  spacewalk-java-1.2.39-64.el6sat.noarch
Sat 5.4.0:
  spacewalk-backend-tools-1.2.13-38.el5sat
  spacewalk-java-1.2.39-45.el5sat


How reproducible:
always


Steps to Reproduce:
1. Create channel and repo, put them together, start repo sync
2. Ensure repo sync is in progress
   # ps ax | grep sync
   751 ? S 0:04 /usr/bin/python -u /usr/bin/spacewalk-repo-sync --channel test-sync --type yum
3. Using WebUI attempt to delete the channel
   Channels -> Manage Software Channels -> <your_channel> -> delete software channel


Actual results:
Channel gets deleted, but repo sync is still running.


Expected results:
I should net be allowed to delete the channel, or repo sync should be terminated. Also in case channel had repetitive sync scheduled, relevant taskomatic bunch should be removed.


Additional info:
This was noticed during testing of bug 663326.