Newly deployed modelendpoint pods are failing in CrashLoopBackOff state.
While connected to the PAIS cluster context where the modelendpoint pods are deploying, the following symptoms are observed:
kubectl describe pod -n <modelendpoint namespace> <modelendpoint pod>
kubectl logs -n <modelendpoint namespace> <modelendpoint pod> -c main
ValueError: Free memory on device (<current memory>/<max memory> GiB) on startup is less than desired GPU memory utilization (0.9, <memory> GIB). Decrease GPU memory utilization or reduce GPU memory used by other processes.
RuntimeError: Engine core initialization failed. See root cause above. Failed core proc(s): ()
RuntimeError: CUDA out of memory occurred with warming up sample with <number> dummy requests.Private AI Services v2.1
VMware Cloud Foundation 9.x
A known issue caused by increased VRAM requirements in the LLM engine version used in Private AI services 2.1 that may cause failures with model endpoint deployment.
A new model endpoint will need to be deployed with an override for gpu memory utilization. The fields of an existing model endpoint are immutable and cannot be changed.
Related documentation: Deploy Completion or Embedding Model Endpoints by Using the VCF Automation UI
--gpu_memory_utilization=0.8Modify the memory utilization value as needed for your specific model, but it will need to be a lower value than the amount specified in the error from Issue/Introduction.
Related documentation: Deploy Completion or Embedding Model Endpoints by Using the kubectl Command
inferenceServerCustomization:
cliArgs:
- "--gpu-memory-utilization=0.8"Modify the memory utilization value as needed for your specific model, but it will need to be a lower value than the amount specified in the error from Issue/Introduction.
kubectl apply -f <modelendpoint yaml>