Magento2: "setup:upgrade" disabled for "Table 'mage_1.email_abandoned_cart' doesn't exist"

[fanglexue]

Preconditions (*)

Magento version : 2.3.2
PHP version ：7.2.13
Mysql version : Ver 14.14 Distrib 5.7.22

Steps to reproduce (*)

1. ./bin/magento setup:upgrade
2. report "Upgrading schema.. SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mage_1.email_abandoned_cart' doesn't exist, query was: DESCRIBE email_abandoned_cart"

Expected result (*)

1. "Upgrading schema.. SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mage_1.email_abandoned_cart' doesn't exist, query was: DESCRIBE email_abandoned_cart"

Actual result (*)

1. Correct implementation

[m2-assistant[bot]]

Hi @fanglexue. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@fanglexue do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hello @fanglexue. Thanks for applying. Currently we've been not able to reproduce Your issue. Could You please confirm You are able to reproduce it on a fresh vanilla Magento installation of 2.3-develop version. Thank You.
P.S. We are taking into consideration that You messed up the contents of Your Expected and Actual results. If it's not so please let us know.

[fluential]

I am having similar issue when upgrading from 2.2.3 db to 2.3.2, the issue is that
vendor/dotmailer/dotmailer-magento2-extension/Setup/InstallSchema.php is not invoked during setup:upgrade related issue here

• https://stackoverflow.com/questions/37745246/magento-2-installschema-not-being-executed
• https://stackoverflow.com/questions/57792783/magento-2-3-setup-installschema-script-not-creating-table

@fanglexue the fix seems to be:

# Drop table
# > delete from setup_module WHERE module='Dotdigitalgroup_Email';
# re-run upgrade
# > setup:upgrade

[fanglexue]

@fluential Thank you for your kind help !