Bug 1393416 - Unable to disable a task schedule
Summary: Unable to disable a task schedule
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-09 13:56 UTC by Kenny Tordeurs
Modified: 2018-04-09 15:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-09 15:10:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kenny Tordeurs 2016-11-09 13:56:12 UTC
Description of problem:
When trying to disable a task schedule trough the webui via:
Admin => Task Schedules => channel-repodata-default 

Check the Disable schedule and then click on edit schedule it proposes to delete the schedule instead of disabling it.

Version-Release number of selected component (if applicable):
Satellite 5.7
satellite-schema-5.7.0.24-1.el6sat.noarch
spacewalk-schema-2.3.2-27.el6sat.noarch


How reproducible:
100%

Steps to Reproduce:
Admin => Task Schedules => channel-repodata-default 

Check the Disable schedule and then click on edit schedule it proposes to delete the schedule instead of disabling it.

Actual results:
Deletes the schedule

Expected results:
Disables the schedule

Additional info:

Comment 2 Tomas Lestach 2016-11-10 15:14:35 UTC
Hello Kenny,

this is expected and designed this way. Disabling and deleting a schedule (so the reoccurring execution of a certain task) is effectively the same thing.
With both - disabling and deleting a schedule you're telling from now on you do not want the task to be executed on a periodic basis.


I agree the wording isn't consistent though.

Comment 3 Kenny Tordeurs 2016-11-10 15:18:07 UTC
Hi Tomas,

Thanks for the quick reply.

Would be nice if we could change it to delete instead of disable to avoid confusion. Because disable would make you think you can enable it again while now you would have to re-create the schedule.

Comment 4 Tomas Lestach 2018-04-09 15:10:26 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.


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