-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ascend for Volcano get "Fail to load custom plugins: plugin: not implemented" #3959
Comments
Hi, thank you for your issue, please translate into English first, which can allow users around the world to understand, thanks :) |
Please ask in https://gitee.com/ascend/ascend-for-volcano |
Hi, did you delete the arg |
https://gitee.com/ascend/mind-cluster/blob/master/component/ascend-for-volcano/build/build.sh ![]() no changes |
I have met the same problem :( |
I have resolved this problem by using ascend official vocano images. |
Please describe your problem in detail
Use Volcano to schedule Huawei 910B series NPU cards and extend it by integrating Ascend plugins based on the open-source Volcano. Reference documentation:
https://www.hiascend.com/document/detail/zh/mindx-dl/600/clusterscheduling/clusterschedulingig/clusterschedulingig/dlug_installation_023.html
Base Informations:
then execute the following command:
I have got volcano-scheduler's POD with CrashLoopBackOff status, the pod's logs :
pod events:
Since this document involves building an NPU scheduling plugin, and there is no relevant error message after following the operations in the official document, it is tentatively assumed that the building of the plugin is normal. During the troubleshooting process, I have read the relevant code logic in VOLCANO 1.9.0 regarding the loading of plugins when the scheduler starts. However, judging from the code (interpreting the code according to the structured programming mindset), it seems that "plugin: not implemented" is an error that is bound to occur (I'm not very familiar with the dynamic plugin mechanism of GO).
If the community has some experiences and ideas on solving this problem, I hope they can be discussed and shared in this issue.
The text was updated successfully, but these errors were encountered: