[None][infra] Bump etcd to 3.6.9 to involve grpc fix

[yuanjingx87]

Summary by CodeRabbit

• Chores
  • Updated etcd installation to version 3.6.9.

Description

Bump etcd which involves a vulnerability fix for grpc

Test Coverage

PR Checklist

Please review the following before submitting your PR:

• PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

• PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

• Test cases are provided for new code paths (see test instructions)

• Any new dependencies have been scanned for license and vulnerabilities

• CODEOWNERS updated if ownership changes

• Documentation updated as needed

• Update tava architecture diagram if there is a significant design change in PR.

• The reviewers assigned automatically/manually are appropriate for the PR.

• Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

To see a list of available CI bot commands, please comment /bot help.

[coderabbitai]

📝 Walkthrough

Walkthrough

The etcd installation script is updated to install version v3.6.9 instead of v3.5.21 by modifying the ETCD_VER variable. The download URL path and tarball filename are adjusted accordingly, while all other installation logic remains unchanged.

Changes

Cohort / File(s)	Summary
etcd Version Update docker/common/install_etcd.sh	Updated ETCD_VER constant from v3.5.21 to v3.6.9, which changes the constructed download URL and tarball name used during installation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	PR title is properly formatted with ticket and type. However, the Description section is minimal, lacking detailed explanation of the vulnerability fix and rationale beyond brief mention.	Expand the Description section to explain the specific gRPC vulnerability being fixed, the impact of the vulnerability, and why upgrading etcd to 3.6.9 addresses it. Also clarify Test Coverage section expectations.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping etcd to version 3.6.9 to address a gRPC vulnerability fix, which directly matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[yuanjingx87]

/bot run --stage-list "Build-Docker-Images"

[tensorrt-cicd]

PR_Github #40762 [ run ] triggered by Bot. Commit: 71560b2 Link to invocation

[tensorrt-cicd]

PR_Github #40762 [ run ] completed with state SUCCESS. Commit: 71560b2
/LLM/main/L0_MergeRequest_PR pipeline #31779 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[yuanjingx87]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #40894 [ run ] triggered by Bot. Commit: f28c2f1 Link to invocation

[tensorrt-cicd]

PR_Github #40894 [ run ] completed with state FAILURE. Commit: f28c2f1
/LLM/main/L0_MergeRequest_PR pipeline #31896 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[yuanjingx87]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #40983 [ run ] triggered by Bot. Commit: f28c2f1 Link to invocation

[tensorrt-cicd]

PR_Github #40983 [ run ] completed with state FAILURE. Commit: f28c2f1
/LLM/main/L0_MergeRequest_PR pipeline #31965 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[yuanjingx87]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #41035 [ run ] triggered by Bot. Commit: a3e4daf Link to invocation

[tensorrt-cicd]

PR_Github #41035 [ run ] completed with state SUCCESS. Commit: a3e4daf
/LLM/main/L0_MergeRequest_PR pipeline #32015 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[yuanjingx87]

/bot run --stage-list "Build-Docker-Images"

[tensorrt-cicd]

PR_Github #41240 [ run ] triggered by Bot. Commit: d7a2c95 Link to invocation

[yuanjingx87]

/bot run --stage-list "Build-Docker-Images"

[yuanjingx87]

/bot run --stage-list "Build-Docker-Images"

[tensorrt-cicd]

PR_Github #41313 [ run ] triggered by Bot. Commit: d7a2c95 Link to invocation

[yuanjingx87]

/bot run --stage-list "Build-Docker-Images"

[tensorrt-cicd]

PR_Github #41473 [ run ] triggered by Bot. Commit: d185b54 Link to invocation

[tensorrt-cicd]

PR_Github #41473 [ run ] completed with state FAILURE. Commit: d185b54
/LLM/main/L0_MergeRequest_PR pipeline #32399 (Partly Tested) completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[niukuo]

/bot skip --comment "docker build stage pass"

[tensorrt-cicd]

PR_Github #42343 [ skip ] triggered by Bot. Commit: d185b54 Link to invocation

[tensorrt-cicd]

PR_Github #42343 [ skip ] completed with state SUCCESS. Commit: d185b54
Skipping testing for commit d185b54

Link to invocation