-
Bug
-
Resolution: Fixed
-
Minor
-
4.0, 4.0.5
-
MOODLE_400_STABLE
-
MOODLE_400_STABLE
-
MDL-74558-master -
When we delete a BBB activity, Moodle sends an end_meeting request. BBB returns the error message below:
Execute adhoc task: core_course\task\course_delete_modules
|
... started 21:12:25. Current memory use 8.6 MB. |
++ Entity not found : {"meetingid":"cc2c3d38a0c0f6ef512503173d32dc5bf168ab73-2-1[0]","xmlmessage":"We could not find a meeting with that meeting ID - perhaps the meeting is not yet running?"}. ++ |
* line 466 of /mod/bigbluebuttonbn/classes/local/proxy/bigbluebutton_proxy.php: call to mod_bigbluebuttonbn\local\proxy\proxy_base::assert_returned_xml() |
* line 187 of /mod/bigbluebuttonbn/classes/meeting.php: call to mod_bigbluebuttonbn\local\proxy\bigbluebutton_proxy::end_meeting() |
* line 161 of /mod/bigbluebuttonbn/lib.php: call to mod_bigbluebuttonbn\meeting->end_meeting() |
* line 900 of /course/lib.php: call to bigbluebuttonbn_delete_instance() |
* line 66 of /course/classes/task/course_delete_modules.php: call to course_delete_module() |
* line 341 of /lib/cronlib.php: call to core_course\task\course_delete_modules->execute() |
* line 198 of /lib/cronlib.php: call to cron_run_inner_adhoc_task() |
* line 76 of /lib/cronlib.php: call to cron_run_adhoc_tasks() |
* line 81 of /admin/cron.php: call to cron_run() |
... used 255 dbqueries |
... used 0.77006506919861 seconds |
Adhoc task complete: core_course\task\course_delete_modules
|
This could lead to false positives as this error message is displayed because the meeting does not exist at the time of activity deletion.
The error appears the same in moosh when performing the category-delete command
STEPS TO REPRODUCE:
- Login as admin
- Create BBB activity
- Delete the activity
- Run cron.
A possible workaround would be to not use the activity at all, but we would need to change logic.
- duplicates
-
-
- Closed
-
