Yes. True. For OP's version of Moodle 7.3 of PHP is supposed to be fine, but ... stuck in upgrading plugins loop and OP didn't share what additional plugins (non core) were installed. MIght be faulty human logic (mine), but by rolling back PHP and CLI upgrade script the bug in an addon plugin might show.
I install moosh now on new systems and collect the shortnames of all additional plugins (not core). Then run moosh command with grep to pull out just the non-core plugins info for version compatibility for those addons.
addons.txt contents
format_topcoll
report_benchmark
report_coursesize
local_mailtest
checkaddons script
#!/bin/bash
#
echo 'Add-on listing: ';
cat ./addons.txt;
echo '---------------------';
for i in `cat ./addons.txt`
do
echo "Addon in que: $i";
moosh -n plugin-list |grep $i
done
For this specific example, a Moodle 3.7.highest
Execution of above results in display of this:
Add-on listing:
format_topcoll
report_benchmark
report_coursesize
local_mailtest
---------------------
Addon in que: format_topcoll
format_topcoll,1.9,2.0,2.1,2.2,2.3,2.4,2.5,2.6,2.7,2.8,2.9,3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,https:// moodle.org/plugins/download.php/21284/format_topcoll_moodle38_2019111701.zip
Addon in que: report_benchmark
report_benchmark,3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,https:// moodle.org/plugins/download.php/21093/report_benchmark_moodle38_2020022400.zip
Addon in que: report_coursesize
report_coursesize,2.3,2.4,2.5,2.6,2.7,2.8,2.9,3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,https:// moodle.org/plugins/download.php/19641/report_coursesize_moodle37_2019052800.zip
Addon in que: local_mailtest
local_mailtest,2.5,2.6,2.7,2.8,2.9,3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,https:// moodle.org/plugins/download.php/20592/local_mailtest_moodle38_2019111700.zip
If am considering upgrading this 3.7 instance to 3.8.highest, am then alerted to *possible* issue with report_coursesize as Moodle plugins shows compat up to 3.7.
Oh, yeah ... the url's above would have been clickable here had I not added a space after https:// On servers I sometimes use above to build a plugingetlist and wget them to a pluginarchive folder that can then be transported to another moodle instance ... building a dev instance of production comes to mind.
'SoS', Ken