Skip to content

Backport PR 4338 to Release 2.0 - #4447

Open
aadvani-nvidia wants to merge 1 commit into
NVIDIA:release/v2.0from
aadvani-nvidia:backport/release-v2.0/pr-4338
Open

Backport PR 4338 to Release 2.0#4447
aadvani-nvidia wants to merge 1 commit into
NVIDIA:release/v2.0from
aadvani-nvidia:backport/release-v2.0/pr-4338

Conversation

@aadvani-nvidia

Copy link
Copy Markdown
Contributor

Backport PR 4338 to Release 2.0.

Related issues

PR 4338

Type of Change

  • Add - New feature or capability
  • Change - Changes in existing functionality
  • Fix - Bug fixes
  • Remove - Removed features or deprecated functionality
  • Internal - Internal changes (refactoring, tests, docs, etc.)

Breaking Changes

  • This PR contains breaking changes

Testing

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed
  • No testing required (docs, internal refactor, etc.)

Additional Notes

(cherry picked from commit 1d2f5e5)

Description:

In FNN mode with an L3 Physical tenant interface (is_l2_segment is
false), the FMDS instance metadata gateway address (169.254.169.253/30)
was never configured on the DPU in container mode.

Root cause: fmds_gateway_vlan is determined by finding the first
Physical-typed interface in tenant_interfaces. In FNN deployments, the
Physical interface (pf0hpf_if) is typically an L3 linknet, so
HasFmdsGateway is true was correctly set on that port. However,
nvue_startup_fnn.conf only rendered 169.254.169.253/30 inside the
IsL2Segment SVI block. The L3 interface IP block had no equivalent
check.

Fix:
  - Added HasFmdsGateway true check to the L3 interface IP block.
  - Added 3 tests via AI

## Related issues
https://nvbugspro.nvidia.com/bug/6533524

## Type of Change
- [ ] **Add** - New feature or capability
- [ ] **Change** - Changes in existing functionality
- [ x] **Fix** - Bug fixes
- [ ] **Remove** - Removed features or deprecated functionality
- [ ] **Internal** - Internal changes (refactoring, tests, docs, etc.)

## Breaking Changes
- [ ] **This PR contains breaking changes**

## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] No testing required (docs, internal refactor, etc.)

## Additional Notes
Don't have a setup for testing, will be tested on demo2 once the fix is
in.

(cherry picked from commit 1d2f5e5)
@aadvani-nvidia
aadvani-nvidia requested a review from a team July 31, 2026 17:37
@coderabbitai

coderabbitai Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b7da3af6-e906-44ea-8fe2-6e6b9e7d43b3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

🔐 TruffleHog Secret Scan

No secrets or credentials found!

Your code has been scanned for 700+ types of secrets and credentials. All clear! 🎉

🔗 View scan details

🕐 Last updated: 2026-07-31 17:42:37 UTC | Commit: 89c4694

@github-actions

github-actions Bot commented Jul 31, 2026

Copy link
Copy Markdown

🔍 Container Scan Summary

Service Total Critical High Medium Low Other
boot-artifacts-aarch64 3 0 0 3 0 0
boot-artifacts-x86_64 3 0 0 3 0 0
forge-admin-cli-x86_64 266 16 33 79 7 131
machine-validation-runner 562 41 125 188 20 188
machine_validation 562 41 125 188 20 188
machine_validation-aarch64 562 41 125 188 20 188
nvmetal-carbide 562 41 125 188 20 188
TOTAL 2520 180 533 837 87 883

Per-CVE detail lives in the per-service grype-* artifacts (JSON + SARIF). Severity counts only — no CVE IDs published here.

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.

1 participant