You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@yunikorn.apache.org by "Manikandan R (Jira)" <ji...@apache.org> on 2026/02/10 04:46:00 UTC

[jira] [Resolved] (YUNIKORN-3226) Remove event creation for succeeded / deleted pods

     [ https://issues.apache.org/jira/browse/YUNIKORN-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikandan R resolved YUNIKORN-3226.
------------------------------------
    Fix Version/s: 1.9.0
       Resolution: Fixed

> Remove event creation for succeeded / deleted pods
> --------------------------------------------------
>
>                 Key: YUNIKORN-3226
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-3226
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Manikandan R
>            Assignee: Manikandan R
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>
> In the scheduler when a pod succeeds and then gets deleted the event that gets generated by YuniKorn shows up as a rejected event much later, minutes, in the YuniKorn logs.
> YuniKorn build info:
>  
>  {{"buildDate": "2023-02-16T06:06:07+0000","buildVersion": "1.2.0-b4","isPluginVersion": "false",}}
> Not sure if this is specific for placeholder pods only or if this is a generic issue.
> This is really confusing and has to stop as it impacts issue analysis. It also triggers redirecting of cases to YuniKorn to investigate as being the root cause of an issue which might not exist.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org