Skip to content

[Bugfix] Use dashes instead of underscores for --gpu-memory-utilization flag - #1124

Merged
ruizhang0101 merged 1 commit into
vllm-project:mainfrom
antar-ghuman:fix/gpu-memory-utilization-flag
Oct 7, 2026
Merged

ruizhang0101 merged 1 commit into
vllm-project:mainfrom
antar-ghuman:fix/gpu-memory-utilization-flag

Conversation

@antar-ghuman

Copy link
Copy Markdown
Contributor

Summary

Fixes inconsistency in CLI flag formatting by replacing underscores with dashes in the --gpu-memory-utilization flag across templates, test files, and controller code.

Changes

  • Update helm/templates/deployment-vllm-multi.yaml
  • Update helm/tests/deployment-vllm-multi_test.yaml
  • Update operator/internal/controller/vllmruntime_controller.go

This ensures the flag matches the correct CLI argument format and maintains consistency across the codebase.

Checklist

  • Make sure the code changes pass the pre-commit checks.
  • Sign-off your commit by using -s when doing git commit
  • Classified PR as [Bugfix]

- Update helm/templates/deployment-vllm-multi.yaml
- Update helm/tests/deployment-vllm-multi_test.yaml
- Update operator/internal/controller/vllmruntime_controller.go

Fixes inconsistency in CLI flag formatting across test files and controller code.

Signed-off-by: antar-ghuman <antarghuman82@gmail.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the command-line argument for GPU memory utilization from --gpu_memory_utilization to --gpu-memory-utilization across the Helm templates, Helm tests, and the vLLM runtime controller to ensure consistency with the expected vLLM CLI argument format. There are no review comments, and I have no additional feedback to provide.

@ruizhang0101 ruizhang0101 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ruizhang0101
ruizhang0101 enabled auto-merge (squash) October 7, 2026 18:24
@ruizhang0101
ruizhang0101 merged commit 4e076e8 into vllm-project:main Oct 7, 2026
13 checks passed
rahulssv-ibm added a commit to rahulssv-ibm/production-stack that referenced this pull request Oct 20, 2026
The Helm chart and the operator pass `--max_loras` to `vllm serve`, while
vLLM documents its engine args with dashes (`--max-loras`). The Ray cluster
template already uses `--max-loras`. This is the same issue reported for
`--gpu-memory-utilization` in vllm-project#1116; that flag was fixed in vllm-project#1124, but
`--max_loras` was left behind.

- helm: emit `--max-loras` in deployment-vllm-multi.yaml
- operator: emit `--max-loras` in the VLLMRuntime deployment builder
- add a helm unittest asserting `--max-loras` is rendered
- add an operator unit test asserting the vLLM args use dashes

Fixes vllm-project#1116

Signed-off-by: Rahul <Rahul.Vishwakarma2@ibm.com>
rahulssv-ibm added a commit to rahulssv-ibm/production-stack that referenced this pull request Oct 20, 2026
The Helm chart and the operator pass `--max_loras` to `vllm serve`, while
vLLM documents its engine args with dashes (`--max-loras`) and the Ray
cluster template already uses `--max-loras`. vLLM's argument parser also
accepts the underscore form, so this aligns the flag with the documented
name rather than fixing a startup failure.

This is the same issue reported for `--gpu-memory-utilization` in vllm-project#1116;
that flag was fixed in vllm-project#1124, which left `--max_loras` behind.

Fixes vllm-project#1116

Signed-off-by: Rahul <Rahul.Vishwakarma2@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants