[asterisk-bugs] [JIRA] (ASTERISK-21035) [patch] - features.conf in static realtime requires distinct cat_metric for each parking lot

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21035:
-----------------------------------

    Summary: [patch] - features.conf in static realtime requires distinct cat_metric for each parking lot   (was: features.conf in static realtime requires distinct cat_metric for each parking lot )
    
> [patch] - features.conf in static realtime requires distinct cat_metric for each parking lot 
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21035
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21035
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/res_config_mysql
>    Affects Versions: 1.8.20.0
>         Environment: CentOS, res_config_mysql backend
>            Reporter: Alex Epshteyn
>            Assignee: Alex Epshteyn
>         Attachments: asterisk-21035-orderby.diff, cli, static_db.sql
>
>
> when multiple parking lots are defined in static realtime even though each parking lot has a distinct category but cat_metric is the same for all parking lots produces errors during configuration load or "features reload". Making cat_metric unique for each parking lot seems  to solve the problem. It appears that the problem may be related to the order of loading of the configuration data (tested only using res_config_mysql)

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