[asterisk-bugs] [JIRA] (ASTERISK-27897) tests/manager/acl-login: An AMI Login was allowed which was not expected.

[Alexander Traud (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243732#comment-243732 ] 

Alexander Traud commented on ASTERISK-27897:
--------------------------------------------

The same happens in Fedora 28. The steps are the same except for the packages below. However, {{asttest}} must be patched to use Lua 5.1.
{code}# Asterisk (essential)
sudo yum install make gcc gcc-c++ pkgconfig libedit-devel jansson-devel libuuid-devel sqlite-devel libxslt-devel
# Asterisk (optional)
sudo yum install binutils-devel libcurl-devel compat-lua-devel python2-devel spandsp-devel speex-devel speexdsp-devel sqlite2-devel libsrtp-devel openssl-devel unbound-devel xmlstarlet bash
# SIPp
sudo yum install make gcc-c++ autoconf automake help2man ncurses-devel openssl-devel patch
# yappcap
sudo yum install make gcc redhat-rpm-config libpcap-devel python2-Cython python2-devel
# asttest
sudo yum install make gcc pkgconfig compat-lua compat-lua-devel patch
# starpy
sudo yum install git python2 python2-setuptools
# Asterisk Test Suite
sudo yum install python2 python2-autobahn python2-construct python2-lxml python2-netifaces python2-numpy python2-PyXB python2-requests python2-twisted python2-pyyaml{code}

> tests/manager/acl-login: An AMI Login was allowed which was not expected.
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-27897
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27897
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Tests/testsuite
>    Affects Versions: GIT
>         Environment: Fedora 28
> Ubuntu 18.04 LTS
>            Reporter: Alexander Traud
>
> {{tests/manager/acl-login}} from the Asterisk Test Suite fails for me constantly, with the following errors:{code}ami_connect: AMI  4: Login was allowed and it shouldn't have been.
> ami_connect: AMI  6: Login was allowed and it shouldn't have been.
> ami_connect: AMI  7: Login was allowed and it shouldn't have been.
> ami_connect: AMI  9: Login was allowed and it shouldn't have been.
> ami_connect: AMI 11: Login was allowed and it shouldn't have been.
> ami_connect: AMI 12: Login was allowed and it shouldn't have been.
> ami_connect: AMI 13: Login was allowed and it shouldn't have been.
> ami_connect: AMI 14: Login was allowed and it shouldn't have been.
> ami_connect: AMI 10: Login was allowed and it shouldn't have been.
> ami_connect: AMI 15: Login was allowed and it shouldn't have been.
> evaluate_success: An AMI login was allowed which was not expected.{code}The IDs change and shuffle, not sure if that matters. No idea what is causing this. Someone has to take over.



--
This message was sent by Atlassian JIRA
(v6.2#6252)