[asterisk-bugs] [JIRA] (ASTERISK-23350) Testsuite: manager/acl-login fails on some platforms

[Corey Farrell (JIRA)]

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

Corey Farrell commented on ASTERISK-23350:
------------------------------------------

For starpy should I send a pull request through github?

Also note the testsuite patch probably requires the starpy patch, I'm not sure what would happen with patched testsuite and non-patched starpy.
                
> Testsuite: manager/acl-login fails on some platforms
> ----------------------------------------------------
>
>                 Key: ASTERISK-23350
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23350
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Tests/testsuite
>    Affects Versions: SVN
>         Environment: Linux ws2 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Corey Farrell
>            Severity: Minor
>         Attachments: starpy-manager-bindAddress.patch, testsuite-manager-acl-login-bindAddress.patch
>
>
> tests/manager/acl-login assumes that an AMI connection to 127.0.0.2 will be sent from 127.0.0.2.  On some systems all connections to 127.0.0.x are made from 127.0.0.1 by default.
> * starpy/manager.py needs to accept named parameter bindAddress, for use with reactor.connectTCP.
> * acl-login test needs to specify bindAddress for manager connections.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira