[YUNIKORN-675] Pod status update could fail due to conflicts

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.11
• Component/s: shim - kubernetes
• Target Version: 0.11
• Assignee: Chaoran Yu
• Reporter: Chaoran Yu
• Created: 19/May/21 16:05
• Updated: 21/Jan/22 21:48
• Resolved: 02/Jun/21 04:04

Description

https://issues.apache.org/jira/browse/YUNIKORN-657 introduced a change that set the pods to failed status when there's an application scheduling error. But the update of pod status may occasionally fail due to conflicts (e.g. the pods have been modified elsewhere). Need to get the latest pod before applying the status update. Also retry with exponential backoff if conflicts still exist

Issue Links

• is caused by: YUNIKORN-657 Expose reason of application failure to pods