[YUNIKORN-480] root queue max resource gets reset on config load

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.10
• Fix Version/s: 0.10
• Component/s: core - scheduler
• Labels: pull-request-available
• Target Version: 0.10
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 08/Dec/20 09:00
• Updated: 21/Jan/22 21:48
• Resolved: 10/Dec/20 08:54

Description

When updating the configuration the root queue max resource is getting reset to nil. The configuration should never set the root queue resources. On creation of the queue this is not a problem as there cannot be any registered node. On update we have registered nodes and should thus not clear it out.

When the max resource gets reset it stops allocation as the scheduler thinks there are no nodes registered and nothing can be done.

Found by the e2e tests as part of the shim dependency change YUNIKORN-475

Issue Links

• blocks: YUNIKORN-475 Move shim build to core without cache
• is caused by: YUNIKORN-317 Cache/Scheduler modules need to be combined to a single module
• links to: GitHub Pull Request #227