Describe the bug
per_component_reboot_test.go actively validates component state telemetry leaves during test execution:
/components/component/state/removable (lines 423, 427, 488, 517)/components/component/state/name (line 257)/components/component/state/oper-status (line 579)
However, these three OpenConfig telemetry paths were left commented out under ## OpenConfig Path and RPC Coverage in feature/gnoi/system/tests/per_component_reboot_test/README.md.
To Reproduce
Steps to reproduce:
- Open
feature/gnoi/system/tests/per_component_reboot_test/per_component_reboot_test.go and inspect lines 257, 427, 488, 517, 579.
- Compare with
feature/gnoi/system/tests/per_component_reboot_test/README.md lines 44-54.
Expected behavior
README.md should document all OpenConfig state paths tested in Go code, annotate component paths with platform_type constraints, and include a valid ## Canonical OC block.
Describe the bug
per_component_reboot_test.goactively validates component state telemetry leaves during test execution:/components/component/state/removable(lines 423, 427, 488, 517)/components/component/state/name(line 257)/components/component/state/oper-status(line 579)However, these three OpenConfig telemetry paths were left commented out under
## OpenConfig Path and RPC Coverageinfeature/gnoi/system/tests/per_component_reboot_test/README.md.To Reproduce
Steps to reproduce:
feature/gnoi/system/tests/per_component_reboot_test/per_component_reboot_test.goand inspect lines 257, 427, 488, 517, 579.feature/gnoi/system/tests/per_component_reboot_test/README.mdlines 44-54.Expected behavior
README.mdshould document all OpenConfig state paths tested in Go code, annotate component paths withplatform_typeconstraints, and include a valid## Canonical OCblock.