| Summary: | ASTERISK-30366: app_queue: Fix preserve reason of pause when Asterisk is restared for realtime queues | ||
| Reporter: | Niklas Larsson (pnlarsson) | Labels: | patch |
| Date Opened: | 2022-12-21 06:22:22.000-0600 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | In Progress/In Progress | Components: | Applications/app_queue |
| Versions: | 18.15.1 20.0.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk-30366.patch | |
| Description: | When the Asterisk is restared it does not preserve paused reason for members of realtime queues. This was fixed for non-realtime queues in https://gerrit.asterisk.org/c/asterisk/+/2131/
Patch exists | ||
| Comments: | By: Asterisk Team (asteriskteam) 2022-12-21 06:22:27.594-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: Joshua C. Colp (jcolp) 2022-12-21 06:36:25.718-0600 Do you plan on putting this up on Gerrit, or just attaching it here? By: Niklas Larsson (pnlarsson) 2022-12-21 06:40:47.171-0600 Need to figure out albematic to add the db column By: Niklas Larsson (pnlarsson) 2023-03-22 04:20:01.755-0500 It's been sitting in gerrit for a while now, and it seams jenkis has failed with out of disk error. How do we progress this - what should I do? By: Joshua C. Colp (jcolp) 2023-03-22 04:25:50.214-0500 Jenkins was fixed and I've told it to recheck after which it'll show up for review. By: Joshua C. Colp (jcolp) 2023-03-22 04:31:22.615-0500 the current Jenkins failure is legit: {noformat} 04:29:25 Alembic branches were found for config 04:29:25 5a2247c957d2 (branchpoint) -> f261363a857f (head) -> 4042a0ff4d9f (head) {noformat} It likely needs a rebase and to be updated, as another alembic change is in front of it and there has been a branch. | ||