Running pod displayed as Waiting for init containers by kubectl.

[landerlini]

Hello.
I am updating my plugin to 0.3.7 and I am trying to cope with the new status system (which I like a lot more than the previous one, thanks).

Unfortunately, I cannot have my running pods displayed as Running.

As you know, the plugin sets the containerStatuses and then interlink builds up the summary defining pod phase and reason.

Can you have a look to the containerStatuses below and let me know if there is a legitimate reason for setting reason to Waiting for init containers and I should set the statuses of containers differently or if it is a bug on your side?

Note that the phase field is set correctly to Running so kueue interpret properly the status of the pod and propagates it correctly to the application level. It's just a matter of what kubectl displays.

  containerStatuses:
  - image: ""
    imageID: ""
    lastState: {}
    name: notebook
    ready: true
    restartCount: 0
    state:
      running:
        startedAt: null
  hostIP: 10.42.6.18
  initContainerStatuses:
  - image: ""
    imageID: ""
    lastState: {}
    name: init-sandbox
    ready: false
    restartCount: 0
    state:
      terminated:
        exitCode: 0
        finishedAt: null
        reason: Completed
        startedAt: null
  phase: Running
  podIP: 10.42.6.18
  podIPs:
  - ip: 10.42.6.18
  reason: Waiting for init containers
  startTime: "2025-01-26T10:52:35Z"

[dciangot]

@Bianco95 looks simura to this: #363

maybe we are missing this fix on the init container part as well

[Bianco95]

Hello, thank you for reporting this issue. The problem occurs because the reason field is not being properly updated when the pod status transitions from waiting for init containers. I will address this. Thanks again for bringing it to our attention!