Skip to content

RT-6.1: Missing LLDP system-description and port-id-type telemetry state paths in README.md #5789

Description

@devansh-lodha

Describe the bug
The test specification in feature/lldp/otg_tests/core_lldp_tlv_population_test/README.md omits two LLDP telemetry state paths that are explicitly queried and asserted in core_lldp_tlv_population_test.go:

  1. /lldp/interfaces/interface/neighbors/neighbor/state/port-id-type
  2. /lldp/state/system-description

Additionally, README.md was missing a valid non-empty LLDP Canonical OC JSON block.

To Reproduce
Steps to reproduce the behavior:

  1. Inspect feature/lldp/otg_tests/core_lldp_tlv_population_test/core_lldp_tlv_population_test.go:
    • Line 232 (verifyNodeConfig): Asserts state.GetSystemDescription() != "DUT".
    • Lines 341 & 344 (verifyDUTTelemetry): Evaluates PortIdType against expected peer state using confirm.State.
  2. Inspect feature/lldp/otg_tests/core_lldp_tlv_population_test/README.md and observe missing telemetry state paths under paths: and missing Canonical OC block.

Expected behavior
README.md should register the verified LLDP telemetry state paths, include a valid non-empty LLDP Canonical OC JSON block, and pass validate_readme_ocpaths and validate_readme_canonicalocspec.

Logs
N/A (Specification gap & validator audit)

Network device platform:

  • Device: Universal / OTG Testbed
  • OS: OpenConfig / Ondatra
  • Version of the test: main branch (core_lldp_tlv_population_test)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions