You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2020/04/16 20:57:00 UTC
[jira] [Resolved] (YUNIKORN-95) YuniKorn does not emit
FailedScheduling event to k8s if pod uses non-existing PVC
[ https://issues.apache.org/jira/browse/YUNIKORN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weiwei Yang resolved YUNIKORN-95.
---------------------------------
Fix Version/s: 0.9
Resolution: Fixed
> YuniKorn does not emit FailedScheduling event to k8s if pod uses non-existing PVC
> ---------------------------------------------------------------------------------
>
> Key: YUNIKORN-95
> URL: https://issues.apache.org/jira/browse/YUNIKORN-95
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - yarn
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Critical
> Labels: pull-request-available
> Fix For: 0.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If a pod uses a non-existing PVC, the default-scheduler emit the following event to Kubernetes:
> {noformat}
> Events:
> Type Reason Age From Message
> ---- ------ ---- ---- -------
> Warning FailedScheduling 45s default-scheduler persistentvolumeclaim "ebs-claim-auto" not found
> {noformat}
> YuniKorn does not emit such event, we only know what has happened by checking the logs:
> {noformat}
> 2020-04-10T00:09:06.620Z DEBUG cache/task.go:404 checking PVC {"name": "non-existing-pvc"}
> 2020-04-10T00:09:06.620Z DEBUG cache/application.go:277 task is not ready for scheduling {"appID": "pod-with-non-existing-pvc", "taskID": "5c3961d1-7abf-11ea-b27d-02ea8179ac42", "error": "persistentvolumeclaim \"non-existing-pvc\" not found"}
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org