[asterisk-bugs] [JIRA] (ASTERISK-25430) Testsuite: batched rls subscription failure

[Ashley Sanders (JIRA)]

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

Ashley Sanders commented on ASTERISK-25430:
-------------------------------------------

>From [~kharwell]: Looking into this a bit there are a few of additional things to note:
1. The test does not fail on the agents every run. However, I can pretty much get it to fail every time on my machine.
2. The Asterisk log shows all expected SIP NOTIFY messages being sent.
3. The test is checking up to 5 lists versions. The rls_integrity.check_integrity function seems to be failing when checking the second pass through (list version 1). Meaning list version 0 passes okay, but the next check is failing. After adding a small amount of debug code it looks like on the second pass through the incoming packet contains the data for the last expected NOTIFY (list version 4), thus the mismatch on the multipart body.

>From [~jcolp]: Per Kevin Harwell - he did some light investigation and it looked as though Asterisk was sending out the right stuff, but pcap may not have been picking it up.

> Testsuite: batched rls subscription failure
> -------------------------------------------
>
>                 Key: ASTERISK-25430
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25430
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Tests/testsuite
>            Reporter: Ashley Sanders
>         Attachments: full-ast1.txt, full-run_1.txt
>
>
> The AsteriskTestSuite tests/channels/pjsip/subscriptions/rls/lists/nominal/presence/batched/basic is failing with the following error:
> ERROR[19504]: rls_integrity:378 fail_test: Unexpected number of parts (2) in multipart body
> See https://bamboo.asterisk.org/bamboo/browse/AST-ATTSCD-C664TE-797/test/case/12354891 for more information.



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