Is it platform specific
generic
Importance or Severity
High
Description of the bug
VS tests started failing after redis-py 7.2.0 was released on Feb 16, 2026. The new version added OpenTelemetry instrumentation that unconditionally accesses conn.port when recording metrics, but UnixDomainSocketConnection (used for Unix socket connections in VS tests) doesn't have this attribute. This causes an AttributeError and test fails.
This affects all repositories running VS tests that install redis without version pinning:
sonic-swss
sonic-sairedis
sonic-swss-common
I have filed issue & PR in redis-py this morning: redis/redis-py#3958
Steps to Reproduce
File a PR in sonic-sairedis or sonic-swss and see vs tests fail.
Fail message is:
Bash exited with code '123'
Look up AttributeError in the logs, should see something similar to:
AttributeError: 'UnixDomainSocketConnection' object has no attribute 'port'
Actual Behavior and Expected Behavior
Actual behavior: vtests fail
Expected Behavior: vtests should not fail
Relevant log output
An example PR blocked is sonic-net/sonic-sairedis#1751
Example logs: https://dev.azure.com/mssonic/be1b070f-be15-4154-aade-b1d3bfb17054/_apis/build/builds/1040408/logs/109
Output of show version, show techsupport
Attach files (if any)
Attached is the vs test logs from the Relevant log output section as a txt file.
logs.txt
Is it platform specific
generic
Importance or Severity
High
Description of the bug
VS tests started failing after redis-py 7.2.0 was released on Feb 16, 2026. The new version added OpenTelemetry instrumentation that unconditionally accesses
conn.portwhen recording metrics, butUnixDomainSocketConnection(used for Unix socket connections in VS tests) doesn't have this attribute. This causes an AttributeError and test fails.This affects all repositories running VS tests that install redis without version pinning:
sonic-swsssonic-sairedissonic-swss-commonI have filed issue & PR in redis-py this morning: redis/redis-py#3958
Steps to Reproduce
File a PR in
sonic-sairedisorsonic-swssand see vs tests fail.Fail message is:
Look up
AttributeErrorin the logs, should see something similar to:Actual Behavior and Expected Behavior
Actual behavior: vtests fail
Expected Behavior: vtests should not fail
Relevant log output
An example PR blocked is sonic-net/sonic-sairedis#1751
Example logs: https://dev.azure.com/mssonic/be1b070f-be15-4154-aade-b1d3bfb17054/_apis/build/builds/1040408/logs/109
Output of
show version,show techsupportAttach files (if any)
Attached is the vs test logs from the Relevant log output section as a txt file.
logs.txt