[Home]

Summary:ASTERISK-29284: Conditinals applications are not working with glibc 2.17-322
Reporter:Igor Olhovskiy (IhorOlkhovskyi)Labels:
Date Opened:2021-02-09 02:57:02.000-0600Date Closed:2021-02-09 04:34:42.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/General
Versions:13.33.0 13.38.0 18.0.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:CentOS 7 (7.9.2009), Kernel 3.10.0-1160.6.1.el7.x86_64Attachments:
Description:Conditional applications like ExecIF, GotoIF behaves incorrectly when evaluating expressions.
Example
{noformat}
[default]
exten => *100,1,NoOP(Hello there)
same => n,ExecIf($["${CALL_ORIGIN}"="APP"]?nemo)
same => n,Playback(vm-welcome)
same => n,Hangup()
{noformat}
{noformat}
> ExecIf("PJSIP/100-00000001", "nan?nemo")
{noformat}

Most of the time evaluation result is nan.
Comments:By: Asterisk Team (asteriskteam) 2021-02-09 02:57:04.335-0600

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Igor Olhovskiy (IhorOlkhovskyi) 2021-02-09 02:58:41.200-0600

if any, the solution now is to downgrade
```
yum install yum-plugin-versionlock
yum downgrade glibc-2.17-317.el7.x86_64 glibc-common-2.17-317.el7.x86_64 glibc-devel-2.17-317.el7.x86_64 glibc-headers-2.17-317.el7.x86_64 nscd-2.17-317.el7.x86_64
yum versionlock glibc-* nscd-*
```
By: Joshua C. Colp (jcolp) 2021-02-09 04:03:45.322-0600

This is being tracked by Redhat at https://bugzilla.redhat.com/show_bug.cgi?id=1925204 and as of the last comment it seems they did a bug fix. When it will appear in CentOS itself I do not know.
By: Joshua C. Colp (jcolp) 2021-02-09 04:11:28.262-0600

I don't think there's anything from an Asterisk perspective to do here, since it was a bug in glibc itself.
By: Igor Olhovskiy (IhorOlkhovskyi) 2021-02-09 04:29:32.384-0600

Totally agree. Was not 100% sure it's glibc bug