Skip to content

Add state verification and README coverage for alarm severity, remote syslog, and mount-point storage-component - #6152

Open
ashishpawar-google wants to merge 1 commit into
openconfig:mainfrom
ashishpawar-google:fix/system-alarms-syslog-mountpoints-state
Open

ashishpawar-google wants to merge 1 commit into
openconfig:mainfrom
ashishpawar-google:fix/system-alarms-syslog-mountpoints-state

Conversation

@ashishpawar-google

@ashishpawar-google ashishpawar-google commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds OpenConfig telemetry state verification, README path/canonical OC documentation, and vendor deviations across three feature/system tests:

  1. Health-1.1 (feature/system/health/tests/system_generic_health_check)

    • README.md: Document /system/alarms/alarm/state/severity in the procedure and rename the path section header from Config Parameter coverage to Telemetry Parameter coverage.
  2. TR-6.1 (feature/system/logging/otg_tests/remote_syslog)

    • README.md: Add the ## Canonical OC section covering /system/logging/remote-servers/remote-server config and state leaves.
    • remote_syslog_test.go:
      • Add verifySyslogState to 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/facility and severity across all configured remote syslog servers.
      • Register t.Cleanup before configuring the DUT so cleanup always runs if a step fails.
      • Skip unsupported non-default VRF test cases before modifying interface VRF bindings.
    • proto/metadata.proto, internal/deviations/deviations.go, metadata.textproto:
      • Add syslog_uniform_selector_required for platforms requiring uniform facility/severity selectors across remote syslog servers (Arista).
      • Add syslog_default_ni_state_unsupported for platforms omitting state/network-instance when a remote syslog server is in the default VRF (Arista, Juniper).
      • Add syslog_debug_severity_unsupported for platforms not supporting DEBUG severity in OpenConfig remote syslog selectors (Juniper).
  3. SYS-4.1 (feature/system/mount_points/tests/system_mount_points_state)

    • README.md: Add /system/mount-points/mount-point/state/storage-component to the Summary, Procedure, Canonical OC, and OpenConfig Path Coverage sections.
    • system_mount_points_state_test.go:
      • Verify /system/mount-points/mount-point/state/storage-component when deviations.SystemMountPointStateFt(dut) is not set.
      • Skip ephemeral /run/user/* runtime mount points that may unmount between list and leaf queries, and remove the utilized + available <= size check that fails on filesystems with reserved blocks or shared pools.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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

  • System Health Check Updates: Updated the generic health check to explicitly validate alarm severities and ensure that major or critical system alarms trigger a test failure.
  • Remote Syslog State Verification: Implemented comprehensive state verification for remote syslog servers, ensuring host, source address, network instance, port, and selector configurations match the intended state.
  • Mount Point Storage Component Validation: Added validation for the storage-component leaf in system mount point state checks, including updated documentation and canonical examples.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@OpenConfigBot

OpenConfigBot commented Oct 11, 2026 •

Copy link
Copy Markdown

Pull Request Functional Test Report for #6152 / ab0b375

Virtual Devices

Device Test Status Test Documentation Job Raw Log
Arista cEOS status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Cisco 8000E status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Cisco XRd status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Juniper ncPTX status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Nokia SR Linux status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Openconfig Lemming status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification

Hardware Devices

Device Test Status Test Documentation Raw Log
Arista status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Cisco status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Juniper status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification
Nokia status
status
status
Health-1.1: pending authorization
TR-6.1: pending authorization
SYS-4.1: pending authorization
Health-1.1: Generic Health Check
TR-6.1: Remote Syslog feature config
SYS-4.1: System Mount Points State Verification

Help

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

@ashishpawar-google

Copy link
Copy Markdown
Contributor Author

/gemini-review

@ashishpawar-google
ashishpawar-google force-pushed the fix/system-alarms-syslog-mountpoints-state branch 2 times, most recently from 0b7c713 to 56c64b5 Compare October 17, 2026 15:12
@ashishpawar-google
ashishpawar-google requested a review from a team as a code owner October 17, 2026 15:12
@ashishpawar-google

Copy link
Copy Markdown
Contributor Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

@ashishpawar-google
ashishpawar-google force-pushed the fix/system-alarms-syslog-mountpoints-state branch from 56c64b5 to 5e3d7c3 Compare October 17, 2026 16:46
@ashishpawar-google
ashishpawar-google force-pushed the fix/system-alarms-syslog-mountpoints-state branch from 5e3d7c3 to 136952f Compare October 26, 2026 11:32
Comment thread proto/metadata.proto Resolved
@ashishpawar-google
ashishpawar-google force-pushed the fix/system-alarms-syslog-mountpoints-state branch 2 times, most recently from f200667 to c12d9a1 Compare November 5, 2026 17:13
@ashishpawar-google
ashishpawar-google force-pushed the fix/system-alarms-syslog-mountpoints-state branch from c12d9a1 to ab0b375 Compare November 9, 2026 09:55

This branch has not been deployed

No deployments
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