Issue with Running SAI-Challenger on Physical SONiC Switch

[Binh Nguyen Hiep]

Hi Team,

I encountered an issue while running SAI-Challenger on a physical SONiC switch with the as5835_sonic testbed and Redis DB. The problem occurs consistently across all unit tests, resulting in the following error:

        while len(status) < 3 and attempts > 0:
            assert self.__check_syncd_running(), "FATAL - SyncD has exited or crashed!"
            time.sleep(tout)
            attempts -= 1
            status = self.r.lrange("GETRESPONSE_KEY_VALUE_OP_QUEUE", 0, -1)

        self.r.delete("GETRESPONSE_KEY_VALUE_OP_QUEUE")

>       assert len(status) == 3, f"SAI \"{op[1:]}\" operation failure!"
E       AssertionError: SAI "create" operation failure

It seems that SAI-Challenger stops all SONiC services before running the tests, leaving only the database and syncd running. However, to fetch the status from the GETRESPONSE_KEY_VALUE_OP_QUEUE table, the sonic.target services appear to be required.

Could you provide guidance on resolving this issue?

Thank you,
Binh Nguyen

[Andriy Kokhan]

Hi Binh Nguyen,

To be able to help, more context is needed.

- What version (commit ID) of SAI Challenger (SAI-C) is used?

- Steps used to build & run SAI-C

- SONiC version running on the target device (show version output)

Best regards,

Andriy

--
You received this message because you are subscribed to the Google Groups "sonicproject" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonicproject...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sonicproject/bf015522-0fbb-4f11-8285-6a9662fcc44dn%40googlegroups.com.

[Binh Nguyen Hiep]

Hi Andriy,
Thanks for your help. This is my Testing environment for SAI-C and SONiC:

Latest commit ID of SAI-C: f249b338dd2596c2c511f491720ce47ccefb779a  (main branch).

- Steps used to build & run SAI-C

1/ Copy SAI-C to SONiC switch, goto SAI-C dir

2/Build client Docker image

    ./build.sh -i client -o bullseye
    ./run.sh -i client -o bullseye
    ./exec.sh -i client

3/Run unit test

#pytest -v --testbed=as5835_sonic -k test_hostif_ut.py

Here is the json configuration of as5835 testbed:

as5835_sonic.json:

- SONiC version:

- Lib SAI version:

Best Regards,

Binh Nguyen.

[Andriy Kokhan]

In general, the steps are correct.

But to be able to run TCs, the SAI headers must be compatible (ideally - identical) on both sides - SAI-C client and DUT (libsai in SONiC). Note, currently SAI-C does not have a mechanism to validate this.

The version of SAI used by SAI-C can be found in sai.env file. However, provided details do not contain the information about the SAI version in SONiC. Since its Edgecore proprietary SONiC image, I can not trace the SONiC version to the SAI version. Probably, SONiC syslog file can provide some hints - that's something that I'd suggest you to examine.

Also, the minor comment - to be able to run UTs, you don't need "dataplane" section in as5835_sonic.json

Regards,

Andriy

To view this discussion visit https://groups.google.com/d/msgid/sonicproject/498aff2b-0315-4b84-86bc-3d06fef8e221n%40googlegroups.com.