Magento2: Missing required argument $metadata of Magento\Framework\EntityManager\MetadataPool

[malikt]

Preconditions

1. Magento version 2.1.2
2. PHP 7.0.13
3. MySQL 5.6.34
4. nginx

Steps to reproduce

1. when i run the command php bin/magento setup:upgrade

Expected result

1. It should upgrade the database

Actual result

1. returns the exception as Missing required argument $metadata of Magento\Framework\EntityManager\MetadataPool
   

[caleoroco]

Same Issue but on a new install of 2.0.14 php5.6

[advcha]

@malikt what you've done before? Do you try to install Magento CE 2.0.xx release note on your 2.1.2?

[malikt]

The fresh installation was Mage CE v2.0.5 and then it was upgraded to 2.1.2, however, suddenly i was not able to run the upgrade command any more due to the error.

[abhinavsk90]

Any update on this. Im getting this issue in Prod server and Prod is down for 12 hrs. It was all good till last night around 2 oclock. We observe the server is down in morning. Trying to upgrade but getting this error.

Magento 2.1.7 upgraded from 2.0.13 2 months back and all good since then.

[orlangur]

@abhinavsk90 did you face with this issue trying to upgrade 2.1.7 to 2.1.9 on prod, while on staging all went smoothly? Or such error just started to appear without any action from you side?

[abhinavsk90]

Started without any action from my side. Didn't try to update or do anything. Still on 2.1.7. It just happened on prod. and site is down. :(

[orlangur]

That's strange, usually such error may happen when var/di or var/generation become out of sync. Did you tried to flush all the caches? Can you provide a full exception stack trace?

[abhinavsk90]

Yeah. Strange only. But seems you are right. Seems some how upgrade got triggered and cause the issue. Im restoring the files from backup and trying to sync everything except db. That's for the clue.

I just observe that my magento file in bin has
$application = new Magento\Framework\Console\Cli('Magento CLI', AppInterface::VERSION);
but the back up has
$application = new Magento\Framework\Console\Cli('Magento CLI');

It all started with asking to upgrade the schema for few module in afternoon on prod.

If you know any setting which can trigger update automatically then please help me to disable that.

[orlangur]

There is no such setting on Magento side.

Looks like something on your side downgraded Magento to 2.0.x, as such constant was removed in 2.1.x: https://github.com/magento/magento2/commit/e46a3cfeccae6f8fcd1eb408719f48d2e039c433#diff-162b082e41b9d0990e5dcc7439d19f26L20

[abhinavsk90]

@orlangur any clue why it got downgraded?

[orlangur]

No, this is not builtin Magento feature, some backup management of your env maybe. Try to understand which particular commands were executed on your instance after last backup which caused a trouble.

[abhinavsk90]

Thanks. Ill investigate why this has happened.

[abhinavsk90]

Forgot to mention 1 thing. Seems this has happened once news letter was sent to everyone. I can see the news letter completed around 11:30 this morning and site was down around that time. Most probably after all newsletters were sent.

Any suggestion!!!

[abhinavsk90]

@orlangur My magento downgraded to 2.0.16 as showing on Admin panel. Earlier my version was 2.0.13 which i upgraded to 2.1.7. Now files belongs to 2.1.7 as i restored from back up. lib, vendor and setup folder is of 2.1.7.
Everything is messed up. Prod is running anyhow. Not sure what going to break and when.

Could you please help me to resolve the version issue.

[orlangur]

hi @abhinavsk90, as far as I know there are no configurations on Magento side which would lead to such behavior, like auto-upgrade, auto-downgrade or something. Regarding this you need to understand what exactly is going on on your server (manual CLI commands, some custom cron jobs etc).

To do a safe upgrade you need to run it on separate env first. Ideally it should be staging server with more or less same configuration as prod, but if it's not an option you still can deploy DB dump and code locally to give upgrade a try.

[magento-engcom-team]

@malikt , thank you for your report.
We were not able to reproduce this issue by following the steps you provided. Please provide more detailed steps to reproduce or try to reproduce this issue on a clean installation or latest release.

[magento-engcom-team]

@malikt, we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

[malikt]

sure you can close the ticket, the issue is still there but I had to leave that setup and move with a latest fresh install.