Repository navigation
Add state verification and README coverage for alarm severity, remote syslog, and mount-point storage-component - #6152
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the validation coverage for several OpenConfig telemetry paths across system health, logging, and storage components. By updating test procedures and README documentation, the changes ensure that critical system states are correctly verified and documented, improving the robustness of the system tests. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
Pull Request Functional Test Report for #6152 / ab0b375Virtual Devices
Hardware Devices
|
There was a problem hiding this comment.
Code Review
This pull request enhances several system health, logging, and mount point tests by adding verification for critical alarms, remote syslog state, and storage components. Feedback on the changes highlights opportunities to optimize gNMI queries by batching operations in verifySyslogState and combining redundant queries in TestSystemAlarms. Additionally, it is recommended to register t.Cleanup earlier in the test lifecycle to guarantee proper state reversion in case of early failures.
|
/gemini-review |
0b7c713 to
56c64b5
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request adds new OpenConfig deviations for remote syslog configuration (SyslogUniformSelectorRequired, SyslogDefaultNIStateUnsupported, and SyslogDebugSeverityUnsupported) and integrates them into the remote syslog test suite, alongside a new verifySyslogState function. It also updates the system mount points test to validate the storage-component state and skip ephemeral user runtime mount points. The review feedback points out that the SyslogDebugSeverityUnsupported deviation is overloaded to control unrelated behaviors—specifically, bypassing loopback interface selection and scaling down traffic parameters—and recommends defining dedicated deviations to maintain clean separation of concerns.
56c64b5 to
5e3d7c3
Compare
5e3d7c3 to
136952f
Compare
f200667 to
c12d9a1
Compare
c12d9a1 to
ab0b375
Compare
Summary
Adds OpenConfig telemetry state verification, README path/canonical OC documentation, and vendor deviations across three
feature/systemtests:Health-1.1(feature/system/health/tests/system_generic_health_check)README.md: Document/system/alarms/alarm/state/severityin the procedure and rename the path section header fromConfig Parameter coveragetoTelemetry Parameter coverage.TR-6.1(feature/system/logging/otg_tests/remote_syslog)README.md: Add the## Canonical OCsection covering/system/logging/remote-servers/remote-serverconfig and state leaves.remote_syslog_test.go:verifySyslogStateto verify/system/logging/remote-servers/remote-server/state/host,source-address,network-instance,remote-port, and/system/logging/remote-servers/remote-server/selectors/selector/state/facilityandseverityacross all configured remote syslog servers.t.Cleanupbefore configuring the DUT so cleanup always runs if a step fails.proto/metadata.proto,internal/deviations/deviations.go,metadata.textproto:syslog_uniform_selector_requiredfor platforms requiring uniform facility/severity selectors across remote syslog servers (Arista).syslog_default_ni_state_unsupportedfor platforms omittingstate/network-instancewhen a remote syslog server is in the default VRF (Arista, Juniper).syslog_debug_severity_unsupportedfor platforms not supportingDEBUGseverity in OpenConfig remote syslog selectors (Juniper).SYS-4.1(feature/system/mount_points/tests/system_mount_points_state)README.md: Add/system/mount-points/mount-point/state/storage-componentto the Summary, Procedure, Canonical OC, and OpenConfig Path Coverage sections.system_mount_points_state_test.go:/system/mount-points/mount-point/state/storage-componentwhendeviations.SystemMountPointStateFt(dut)is not set./run/user/*runtime mount points that may unmount between list and leaf queries, and remove theutilized + available <= sizecheck that fails on filesystems with reserved blocks or shared pools.