Summary: | ASTERISK-27897: tests/manager/acl-login: An AMI Login was allowed which was not expected. | ||
Reporter: | Alexander Traud (traud) | Labels: | |
Date Opened: | 2018-06-05 05:30:11 | Date Closed: | |
Priority: | Major | Regression? | |
Status: | Waiting for Feedback/In Progress | Components: | Tests/testsuite |
Versions: | GIT | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Fedora 28 Ubuntu 18.04 LTS | Attachments: | |
Description: | {{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. | ||
Comments: | By: Asterisk Team (asteriskteam) 2018-06-05 05:30:12.313-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Alexander Traud (traud) 2018-06-06 03:21:38.406-0500 This issue does not happen on Ubuntu 16.04 LTS and the branch Asterisk 15.4. Here my steps for both systems: {code}cd ~/Documents sudo apt install build-essential pkg-config libedit-dev libjansson-dev libsqlite3-dev uuid-dev libxslt1-dev sudo apt install libbfd-dev libcurl4-openssl-dev liblua5.1-0-dev libpython2.7-dev libspandsp-dev libspeex-dev libspeexdsp-dev libsqlite0-dev libsrtp0-dev libssl-dev libunbound-dev xmlstarlet bash wget downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz tar -zxf asterisk-*.tar.gz && rm asterisk-*.tar.gz cd asterisk-*/ ./configure --with-pjproject-bundled --enable-dev-mode make menuselect.makeopts ./menuselect/menuselect --enable TEST_FRAMEWORK --enable DONT_OPTIMIZE --disable COMPILE_DOUBLE --enable BETTER_BACKTRACES --enable app_macro --enable app_statsd --enable res_endpoint_stats --enable res_mwi_external --enable res_mwi_external_ami --enable res_stasis_mailbox --enable res_ari_mailboxes --enable codec_opus make sudo make samples config # # SIPp # cd ~/Documents sudo apt install build-essential autoconf automake help2man libncurses5-dev libpcap-dev libssl-dev patch wget github.com/SIPp/sipp/releases/download/v3.5.1/sipp-3.5.1.tar.gz tar -zxf sipp-3.*.tar.gz && rm sipp-3.*.tar.gz cd sipp-*/ wget github.com/SIPp/sipp/commit/10a7b8069f7147c40f278ad77fd0d48c1740274c.patch patch -p1 <./10a7b8069f7147c40f278ad77fd0d48c1740274c.patch ./build.sh --enable-epoll --with-openssl --with-pcap sudo make install # # yappcap # cd ~/Documents sudo apt install build-essential libpcap-dev cython libpython2.7-dev wget github.com/otherwiseguy/yappcap/archive/master.tar.gz tar -zxf master.tar.gz && rm master.tar.gz cd yappcap-*/ make sudo make install # # Test Suite # cd ~/Documents wget github.com/asterisk/testsuite/archive/13.tar.gz tar -zxf master.tar.gz && rm master.tar.gz # # Test Suite (asttest) # cd ~/Documents/testsuite-*/ sudo apt install build-essential pkg-config lua5.1 liblua5.1-0-dev patch cd ./asttest/ make sudo make install # # Test Suite (starpy) # cd ~/Documents/testsuite-*/ sudo apt install git python2.7 python-setuptools make -C ./addons update cd ./addons/starpy/ sudo python ./setup.py install # # Test Suite (run) # cd ~/Documents/testsuite-*/ sudo apt install python2.7 python-autobahn python-construct python-lxml python-netifaces python-numpy python-pyxb python-requests python-twisted python-yaml sudo ./runtests.py --list-tests{code}Because of ASTERISK-27717 (which is not solved, yet), you have to add {{sudo apt install python-dev}} For the test on Ubuntu 18.04 LTS, I did not go for the branch Asterisk 13 but the master branch. By: Alexander Traud (traud) 2018-06-07 06:20:52.148-0500 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 (see ASTERISK-27904). {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} By: Richard Mudgett (rmudgett) 2018-06-26 11:29:25.151-0500 Please attach the log files (testsuite and asterisk) captured by the tests/manager/acl-login test. When a testsuite test fails the logs are stored under the logs directory of the testsuite tree in a similar directory tree. {noformat} sudo ./cleanup-test-remnants.sh sudo ./runtests.py -t tests/manager/acl-login {noformat} |