search

inverse-inc / packetfence

PacketFence is a fully supported, trusted, Free and Open Source network access control (NAC) solution. Boasting an impressive feature set including a captive-portal for registration and remediation, centralized wired and wireless management, powerful BYOD management options, 802.1X support, layer-2 isolation of problematic devices; PacketFence can be used to effectively secure networks small to very large heterogeneous networks.
https://packetfence.org
GNU General Public License v2.0
1.39k stars 291 forks source link

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

Open JeGoi opened 2 months ago

JeGoi commented 2 months ago

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 ?