Skip to content

Relase 0.3.0 - cherry-pick commits 443d31836f4c09a17bfcf8ac1192de02fc6f2585 and 40d7b6a88bf933cf5eec13aa9132bd951db5f247#535

Open
yoks wants to merge 2 commits intoNVIDIA:release/v0.3.0from
yoks:release-agent-cherry
Open

Relase 0.3.0 - cherry-pick commits 443d31836f4c09a17bfcf8ac1192de02fc6f2585 and 40d7b6a88bf933cf5eec13aa9132bd951db5f247#535
yoks wants to merge 2 commits intoNVIDIA:release/v0.3.0from
yoks:release-agent-cherry

Conversation

@yoks
Copy link
Contributor

@yoks yoks commented Mar 12, 2026

No description provided.

wminckler and others added 2 commits March 11, 2026 19:42
…uration (NVIDIA#457)

When applying a new nvue config, it sets the interface to up and for the
non-primary DPUs, agent was going back and bringing the interface down.
This leaves a small window where the host can get a dhcp response,
leaking the admin IP address assigned to the host.

- removes the interface and vpcs from the nvue config
-- bridge was always include in the non-fnn case. this was removed if
not needed
- disables dhcp server (it fails without the vpc)
- ignores the dhcp server health when it is disabled
- instead of bringing down the interface in the container, it brings down the interface on the dpu os, which is reflected in the host. (this is not required, but is a nice to have)
- updates tests

Tested both etv and fnn configs in the dev env.

## Description
<!-- Describe what this PR does -->

## Type of Change
<!-- Check one that best describes this PR -->
- [ ] **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.)

## Related Issues (Optional)
<!-- If applicable, provide GitHub Issue. -->

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

<!-- If checked above, describe the breaking changes and migration steps
-->

## Testing
<!-- How was this tested? Check all that apply -->
- [X] Unit tests added/updated
- [ ] Integration tests added/updated  
- [X] Manual testing performed
- [ ] No testing required (docs, internal refactor, etc.)

## Additional Notes
<!-- Any additional context, deployment notes, or reviewer guidance -->
nvbug # 5931831
## Description
Checking `check_restricted_mode` can break pcie enumeration. This aimed
to reduce this issue by removing it from regular healthcheck

## Type of Change
<!-- Check one that best describes this PR -->
- [ ] **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.)

## Related Issues (Optional)
<!-- If applicable, provide GitHub Issue. -->

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

<!-- If checked above, describe the breaking changes and migration steps
-->

## Testing
<!-- How was this tested? Check all that apply -->
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated  
- [ ] Manual testing performed
- [ ] No testing required (docs, internal refactor, etc.)

## Additional Notes
<!-- Any additional context, deployment notes, or reviewer guidance -->

---------

Signed-off-by: ianisimov <ianisimov@nvidia.com>
@yoks yoks requested a review from a team March 12, 2026 02:44
@yoks yoks requested a review from a team as a code owner March 12, 2026 02:44
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