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

tests: check_radius_reply is failing quite often... #8320

Open
JeGoi opened this issue Sep 23, 2024 · 0 comments
Open

tests: check_radius_reply is failing quite often... #8320

JeGoi opened this issue Sep 23, 2024 · 0 comments
Assignees
Labels
tests Issues related to tests performed by CI

Comments

@JeGoi
Copy link
Contributor

JeGoi commented Sep 23, 2024

Describe the problem
check_radius_reply is falling with 404 as reply from api.

            • check_radius_reply FAILURE
    Testcase "check_radius_reply", step #0: Assertion "result.statuscode ShouldEqual 200" failed. expected: 200  got: 404 (/usr/local/pf/t/venom/test_suites/wired_dot1x_eap_tls_pki/91_check_radius_audit_log.yml:94)
    Testcase "check_radius_reply", step #0: Assertion "result.bodyjson.item.radius_reply ShouldContainSubstring 'Tunnel-Private-Group-Id = \"100\"'" failed. expected '' to contain 'Tunnel-Private-Group-Id = "100"' but it wasn't (/usr/local/pf/t/venom/test_suites/wired_dot1x_eap_tls_pki/91_check_radius_audit_log.yml:0)
    Testcase "check_radius_reply", step #0: Assertion "result.bodyjson.item.profile ShouldEqual \"catch_dot1x_wired_eap_tls\"" failed. expected: catch_dot1x_wired_eap_tls  got: <nil> (/usr/local/pf/t/venom/test_suites/wired_dot1x_eap_tls_pki/91_check_radius_audit_log.yml:0)

Mandatory informations

Symptoms
How the problem can be identified if it appears again ?

@JeGoi JeGoi added the tests Issues related to tests performed by CI label Sep 23, 2024
@JeGoi JeGoi self-assigned this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Issues related to tests performed by CI
Projects
None yet
Development

No branches or pull requests

1 participant