[MGNLSCH-24] Cluster-aware job functionality can break certain use cases Created: 21/Feb/12  Updated: 21/Feb/12  Resolved: 21/Feb/12

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: 1.4.3
Fix Version/s: 1.4.4

Type: Bug Priority: Major
Reporter: Ondrej Chytil Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLSCH-15 Allow tasks to specify cluster node o... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Implementing MGNLSCH-15 prevented possibility to run scheduled jobs on all cluster nodes. Using job for one cluster node should be just optional, not mandatory.
For further details see MGNLSCH-15 ticket.


Generated at Mon Feb 12 10:45:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.