Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: pc/test_po_voq.py::test_po_voq::test_voq_po_update fails with Failed: LAG id 994 for LAG PortChannel999 does not exist in ASIC DB #16172

Open
arista-nwolfe opened this issue Dec 20, 2024 · 0 comments

Comments

@arista-nwolfe
Copy link
Contributor

Issue Description

voq_lag.verify_lag_in_remote_asic_db(remote_duthosts, tmp_lag_id)
   verify_lag_in_asic_db(dut.asics, lag_id, deleted)
      pytest.fail('LAG id {} for LAG {} does not exist in ASIC DB'.format(lag_id, TMP_PC))

The test seems to verify that the LAG id is the same in ASIC_DB on all LCs.
But it seems like it's not found on the remote LC.

Either PortChannel999 doesn't exist on the remote LCs or it's given a different LagId.

for asic in asics:
    asicdb = AsicDbCli(asic)
    asic_db_lag_list = asicdb.get_asic_db_lag_list()
    if deleted:
        ...
    else:
        for lag in asic_db_lag_list:
            if asicdb.hget_key_value(lag, "SAI_LAG_ATTR_SYSTEM_PORT_AGGREGATE_ID") == lag_id:
                logging.info('LAG id {} for LAG {} exist in ASIC DB'.format(lag_id, TMP_PC))
                return
        pytest.fail('LAG id {} for LAG {} does not exist in ASIC DB'.format(lag_id, TMP_PC))

Results you see

LAG_ID is different between LCs for a given portchannel

Results you expected to see

LAG_IDs should be the same on all LCs for a given portchannel

Is it platform specific

generic

Relevant log output

No response

Output of show version

No response

Attach files (if any)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant