Project

General

Profile

Actions

Feature #37938

closed

Reject start-at dates in the past when a job is scheduled

Added by Pablo Fernández Rodríguez almost 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Problem Statement

If a job is scheduled by using `API` or `hammer` and by mistake `start-at` is in the past, the job will be executed immediately. Which most probably is not desired.

Requirements

I would expect the request to be rejected asking to use a valid date.

Actions #1

Updated by The Foreman Bot almost 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/763 added
Actions #2

Updated by The Foreman Bot about 1 year ago

  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman-tasks/pull/768 added
Actions #3

Updated by The Foreman Bot about 1 year ago

  • Pull request deleted (https://github.com/theforeman/foreman-tasks/pull/763, https://github.com/theforeman/foreman-tasks/pull/768)
Actions #4

Updated by Adam Ruzicka about 1 year ago

  • Pull request https://github.com/theforeman/foreman-tasks/pull/768 added
Actions #5

Updated by Pablo Fernández Rodríguez about 1 year ago

  • Status changed from Ready For Testing to Closed
Actions #6

Updated by The Foreman Bot about 1 year ago

  • Pull request https://github.com/theforeman/foreman-tasks/pull/772 added
Actions #7

Updated by Adam Ruzicka about 1 year ago

  • Fixed in Releases foreman_tasks-11.0.2 added
Actions

Also available in: Atom PDF