[YUNIKORN-1793] Handle placement rule and queue changes during initialisation (core)

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: core - common
• Labels: pull-request-available
• Target Version: 1.4.0
• Assignee: Craig Condit
• Reporter: Wilfred Spiegelenburg
• Created: 08/Jun/23 07:56
• Updated: 20/Nov/23 16:42
• Resolved: 30/Aug/23 15:59

Description

If the placement rules change loading an already running workload might fail.

Similar case exists for queue that no longer exist in the config. Even if the queue exists the type could have changed from leaf to parent etc.

Running workloads should never be rejected during init. If a placement fails the application should be placed in a temporary queue. This needs to be restricted to workloads during init only and a queue should be used that cannot be created via the configuration or placement rules.

 

Issue Links

• incorporates: YUNIKORN-19 Use placement rules always
• is duplicated by: YUNIKORN-1623 Handle moved applications after recovery
• links to: GitHub Pull Request #601