#6786 [BUG] CreateContainerError being misclassified as UserError and not honoring retries Issue created by charliemoriarty ### Flyte & Flytekit version flyte version: v1.15.3 flytekit version: v1.16.5 ### Describe the bug When a pod fails to start due to a

ContainersNotReady|CreateContainerError

(particularly "failed to reserve container name"), and the error message includes "Grace period exceeded", the error is incorrectly classified as kind: USER instead of kind: SYSTEM. This causes a gap where neither retry mechanism triggers: • System retries don't apply because the error is classified as USER • User retries don't apply because the container never started and the task code never ran The task fails immediately with no retry attempts, even though retries=5 is configured on the task. ### Expected behavior `ContainersNotReady|CreateContainerError`/grace period exceeded should be classified as a SYSTEM error, which would allow max-node-retries-system-failures to automatically retry the task. Alternatively, user retries should be triggered for pre-execution failures when the error is classified as USER. ### Additional context to reproduce Example error message:

Grace period [3m0s] exceeded|containers with unready status: [primary]|failed to reserve container name "primary_xxxxx_namespace_uuid_0": name "primary_xxxxx_namespace_uuid_0" is reserved for "containerid123..."

Example CRD information:

nodeStatus:
  n0:
    error:
      code: ContainersNotReady|CreateContainerError
      kind: USER
      message: 'Grace period [3m0s] exceeded|containers with unready status: [primary]|failed
        to reserve container name...'
    phase: 6

### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte