Skip to content

Bug:[IPv6 only topo] [test_events.py] test_events.py::test_events is not updated to IPv6 only topology #20758

Description

@OriTrabelsi

Is it platform specific

generic

Importance or Severity

Critical

Description of the bug

test_events.py::test_events is not updated to IPv6 only topology

Steps to Reproduce

run test_events.py::test_events with IPv6 only topology

Actual Behavior and Expected Behavior

During the test we run several times python /root/gnxi/gnmi_cli_py/py_gnmicli.py -g -t {duthost.mgmt_ip} -p 50052 -m subscribe -x all[heartbeat=2] -xt EVENTS -o ndastreamingservertest --subscribe_mode 0 --submode 1 --interval 0 --update_count 1 --create_connections 1 --filter_event_regex and it failes for Error received from peer ipv4:{duthost.mgmt_ip}:50052".

This happens onl for v6 only topology.

Relevant log output

tests.common.errors.RunAnsibleModuleFail: run module shell failed, Ansible Results =>
failed = True
changed = True
end = 2025-09-13 05:27:53.740735
cmd = python /root/gnxi/gnmi_cli_py/py_gnmicli.py -g -t {duthost.mgmt_ip} -p 50052 -m subscribe -x all[heartbeat=2] -xt EVENTS -o ndastreamingservertest --subscribe_mode 0 --submode 1 --interval 0 --update_count 1 --create_connections 1 --filter_event_regex sonic-events-bgp:notification --timeout 30
delta = 0:00:30.174743
rc = 1
invocation = {'module_args': {'creates': None, 'executable': None, '_uses_shell': True, 'strip_empty_ends': True, '_raw_params': 'python /root/gnxi/gnmi_cli_py/py_gnmicli.py -g -t {duthost.mgmt_ip} -p 50052 -m subscribe -x all[heartbeat=2] -xt EVENTS -o ndastreamingservertest --subscribe_mode 0 --submode 1 --interval 0 --update_count 1 --create_connections 1 --filter_event_regex sonic-events-bgp:notification --timeout 30', 'removes': None, 'argv': None, 'warn': False, 'chdir': None, 'stdin_add_newline': True, 'stdin': None}}
start = 2025-09-13 05:27:23.565992
msg = non-zero return code
_ansible_no_log = None
stdout =
Sending SubscribeRequest
subscribe {
  prefix {
    target: "EVENTS"
  }
  subscription {
    path {
      elem {
        name: "all"
        key {
          key: "heartbeat"
          value: "2"
        }
      }
    }
    mode: ON_CHANGE
  }
}

2025-09-13 05:27:25.024957 response received: 
2025-09-13 05:27:26.690739 response received: 
2025-09-13 05:27:28.493345 response received: 
2025-09-13 05:27:30.295669 response received: 
2025-09-13 05:27:32.098111 response received: 
2025-09-13 05:27:33.900597 response received: 
2025-09-13 05:27:35.703071 response received: 
2025-09-13 05:27:37.505599 response received: 
2025-09-13 05:27:39.307955 response received: 
2025-09-13 05:27:41.110300 response received: 
2025-09-13 05:27:42.913395 response received: 
2025-09-13 05:27:44.715725 response received: 
2025-09-13 05:27:46.518067 response received: 
2025-09-13 05:27:48.320398 response received: 
2025-09-13 05:27:50.122736 response received: 
2025-09-13 05:27:51.925176 response received: 
2025-09-13 05:27:53.727559 response received: 
Received an exception from server side and error message is: '<_MultiThreadedRendezvous of RPC that terminated with:
	status = StatusCode.DEADLINE_EXCEEDED
	details = "Deadline Exceeded"
	debug_error_string = "{"created":"@1757730473.718422958","description":"Error received from peer ipv4:{duthost.mgmt_ip}:50052","file":"src/core/lib/surface/call.cc","file_line":1070,"grpc_message":"Deadline Exceeded","grpc_status":4}"
>'.
GRPC error

Output of show version

Attach files (if any)

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions