Closed tdorchak closed 2 months ago
Hello @tdorchak ,
We are aware of this issue, and the fix is planned to be included in 5.17.0. In the meantime, you can apply the attached patch to address failing upgrade script:
Sorry for the trouble!
Thanks, Spencer
Hi @sgabhart22,
When is 5.17.0 expected to release? Seems like it's been quite a while and this issue still occurs for new customers.
I tried to apply the patch above in my local but ran into the following issue: error: Setup/Patch/Data/PerformKeyUpgrade.php: No such file or directory.
~~My files are located here: vendor/amzn/amazon-pay-magento-2-module/Setup/Patch/Data/PerformKeyUpgrade.php~~
Besides that, will this work for my Bitbucket pipeline as the issue is triggering there as well and I currently can't deploy the module because of this.
EDIT: I was able to apply the patch by adding the full directory within the patch. This still doesn't solve the issue for our Bitbucket pipeline though and as such I can't deploy Amazon Pay to our ecommerce store.
Warm regards, Arjen
Hello again @tdorchak and @Hjsurk , version 5.17.0 of the module is now live. Apologies for the long delay!
What I expected
After updating to 5.16.1
bin/magento setup:upgrade
should run the setup scripts to make database updates.What happened instead
When upgrading to 5.16.1 from 5.14 the setup:upgrade is failing because the
core_config_data
table is hardcoded inSetup/Patch/Data/PerformKeyUpgrade.php
instead of dynamically adding a table prefix as many merchants do.Steps to reproduce the issue
composer require amzn/amazon-pay-magento-2-module
bin/magento setup:upgrade
Your setup