magento2: RabbitMQ causes 2.3.1 upgrade failure
Preconditions (*)
- Running M2.2.6
Steps to reproduce (*)
- Upgrade to 2.3.1 as detailed in https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html.
Expected result (*)
- Magento successfully upgrades to 2.3.1
Actual result (*)
- Magento fails to successfully upgrade to 2.3.1
Attempting to run setup:upgrade results in it failing with:
Running schema recurring...
...
Module 'Magento_Amqp':
Notice: Undefined index: save in /home/[site]/public_html/vendor/magento/framework/Reflection/MethodsMap.php on line 81
Disable module Magento_Amqp and it then fails with:
Module 'Magento_MysqlMq':
Running schema recurring...Notice: Undefined index: save in /home/[site]/public_html/vendor/magento/framework/Reflection/MethodsMap.php on line 81
This results in a failed website with:
1 exception(s):
Exception #0 (Magento\Framework\Exception\LocalizedException): Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Klarna_Core data: current version - 4.4.4, required version - 5.1.0
MSP_ReCaptcha data: current version - none, required version - 1.5.0
MSP_TwoFactorAuth data: current version - none, required version - 2.2.0
Amasty_Base data: current version - 1.5.0, required version - 1.6.3
Magento_AuthorizenetAcceptjs data: current version - none, required version - 1.0.0
Klarna_Ordermanagement data: current version - 4.3.4, required version - 5.0.2
Amasty_CronScheduleList data: current version - none, required version - 1.0.0
Klarna_Kp data: current version - 5.4.4, required version - 6.1.0
Temando_Shipping data: current version - 1.2.1, required version - 1.5.0
Vertex_Tax data: current version - 100.2.0, required version - 100.3.0
Exception #0 (Magento\Framework\Exception\LocalizedException): Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Klarna_Core data: current version - 4.4.4, required version - 5.1.0
MSP_ReCaptcha data: current version - none, required version - 1.5.0
MSP_TwoFactorAuth data: current version - none, required version - 2.2.0
Amasty_Base data: current version - 1.5.0, required version - 1.6.3
Magento_AuthorizenetAcceptjs data: current version - none, required version - 1.0.0
Klarna_Ordermanagement data: current version - 4.3.4, required version - 5.0.2
Amasty_CronScheduleList data: current version - none, required version - 1.0.0
Klarna_Kp data: current version - 5.4.4, required version - 6.1.0
Temando_Shipping data: current version - 1.2.1, required version - 1.5.0
Vertex_Tax data: current version - 100.2.0, required version - 100.3.0
<pre>#1 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#0000000056c067c60000000023738766#) called at [vendor/magento/framework/Interception/Interceptor.php:153]
#2 Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', array(&Magento\Framework\App\Request\Http#0000000056c067c60000000023738766#), array(array('default_store_se...', 'page_cache_from_...', 'storeCookieValid...', 'install', 'configHash'))) called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:26]
#3 Magento\Framework\App\FrontController\Interceptor->dispatch(&Magento\Framework\App\Request\Http#0000000056c067c60000000023738766#) called at [vendor/magento/framework/App/Http.php:136]
#4 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:24]
#5 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:258]
#6 Magento\Framework\App\Bootstrap->run(&Magento\Framework\App\Http\Interceptor#0000000056c067840000000023738766#) called at [index.php:39]
</pre>
How do we fix whatever this is that has been added to 2.3 and is causing this failure?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 21 (8 by maintainers)
Hello, I did upgrade from 2.2.3 to 2.3.3 and got the same error:
And it was done successfully only after disabling Magento_Amqp, Magento_MysqlMq. So, the issue still exists despite Magento team unables reproduce it.
Hi, @swatts7777777 thank you for your reply, solved SQL error.
I got some solution to find where the exact problem is occurring.
I was added error log like this
from the above method, we can find where the exact problem is occurring.