Skip to content

feat: use health-override instead of hardware health#518

Merged
yoks merged 10 commits intoNVIDIA:mainfrom
yoks:health-use-overrides
Mar 11, 2026
Merged

feat: use health-override instead of hardware health#518
yoks merged 10 commits intoNVIDIA:mainfrom
yoks:health-use-overrides

Conversation

@yoks
Copy link
Contributor

@yoks yoks commented Mar 11, 2026

Description

With Health-Override API, Hardware-Health API become obsolete. This PR removes this API and moves health service to use overrides instead

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.)

Related Issues (Optional)

Breaking Changes

  • This PR contains breaking changes

HardwareHealthReport API removed

Testing

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

Additional Notes

yoks added 2 commits March 10, 2026 19:25
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
@yoks yoks requested a review from a team as a code owner March 11, 2026 03:07
yoks added 3 commits March 10, 2026 20:22
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
.into_iter()
.filter(|(hr, _)| {
!HealthReportOverrides::is_hardware_health_override_source(&hr.source)
})
Copy link
Contributor

Choose a reason for hiding this comment

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

why remove the hardware reports?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question, at fist i assummed overrides here expected to be only one set by operator. But there is no other source of reports after removal of hardware_health_report, so this filter most likely uncessery.

Copy link
Contributor

Choose a reason for hiding this comment

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

+1. I don't understand why it wouldn't be listed.

Copy link
Contributor

Choose a reason for hiding this comment

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

@yoks Can you clarify?

Copy link
Contributor Author

@yoks yoks Mar 11, 2026

Choose a reason for hiding this comment

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

It was a mistake, i added it to keep test behavior the same, but from functional point of view we now using override for hardware_health, so it would not need to be filtered.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok. Just asking becasue the change is still there :)

.into_iter()
.filter(|(hr, _)| {
!HealthReportOverrides::is_hardware_health_override_source(&hr.source)
})
Copy link
Contributor

Choose a reason for hiding this comment

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

+1. I don't understand why it wouldn't be listed.

yoks added 4 commits March 11, 2026 10:46
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
Signed-off-by: ianisimov <ianisimov@nvidia.com>
@yoks yoks enabled auto-merge (squash) March 11, 2026 21:41
@yoks yoks merged commit 38696ae into NVIDIA:main Mar 11, 2026
33 checks passed
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.

3 participants