Shiva Krishna Merla
Shiva Krishna Merla
yes, thats correct its from the CI.
@ElisaMeng @corbanvilla Can you try with `v1.7.0` and verify if you are still seeing this issue?
@FlorinAndrei for this use case you would need to use a private image(which can be just re-tag of existing centos8 image). ATM there is no plan to continue support for...
@lemaral we had to update each resource for supporting upgrade use cases. This usually happens if reconciliation is triggered quite often and should settle once drivers are loaded and all...
can you paste the output of `kubectl get pods -n gpu-operator` and last logs of operator pod?
@Mutantt Which version of GPU operator are you using? Does validation pod stays in crashloop forever or it does recover?
@Mutantt can you try with 1.5.0 and confirm if you still see this issue?
@Mutantt Are you sure its 1.5.0? Asking because cuda-vecrot-add is no longer a standalone pod like earlier releases. Its added as part of initContainer into device-plugin pods. Can you run...
@Mutantt We have officially not qualified with 460.xx drivers. I will get back to you on this.
@Mutantt If you have attached as passthrough then vGPU drivers are not necessary. Is it possible to attach the VM config info and journal logs from the system?