Bug 701899 - when spacewalk-repo-sync is running for a given channel, I can delete it through WebUI
Summary: when spacewalk-repo-sync is running for a given channel, I can delete it thro...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 540
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2011-05-04 08:44 UTC by Jan Hutař
Modified: 2014-07-04 13:27 UTC (History)
0 users

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


Attachments (Terms of Use)

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.


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