Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Minor
Fix Version/s: 6.18.0
Affects Version/s: None
Component/s: Tasks Plugin
Labels:

Story Points:
3
Target Version:

6.18.0
Blocked:
False
Fixed in Build:
rubygem-foreman-tasks-11.0.4
Severity:
Low
Sprint:
Satellite Endeavour Sprint 1, Satellite Endeavour Sprint 2, Satellite Endeavour Sprint 3, Satellite Endeavour Sprint 4, Satellite Endeavour Sprint 5, Satellite Endeavour Sprint 6
AssignedTeam:
sat-endeavour

Release Note Type:
None
Release Note Text:
None
Release Note Status:
None

PX Impact Score:
PX Review Complete:
SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Test Coverage:

Automated
Regression:
Yes
Preliminary Testing:
Fail

Market:

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.

is duplicated by

SAT-30349 When scheduling a remote job for future execution Satellite allows scheduling remote jobs for past date which causes the job to execute immediately.

Closed

is related to

SAT-37838 Ensure start-at is required for future executions

Closed

SAT-35928 Fix breakage caused by start-at change in f-tasks

Closed

Assignee:: Oleh Fedorenko

Reporter:: Pablo Fernandez Rodriguez

QA Contact:: Lukas Pramuk

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2024/10/02 8:53 AM

Updated:: 2025/10/10 7:29 AM

Resolved:: 2025/10/01 9:56 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates