Magento 2.1 RC1 - Error when running CLI upgrade command

[toddwolaver]

Attempting to run setup:upgrade after compiling DI results in an error. I have tried with just 'setup:upgrade' and 'setup:upgrade --keep-generated'.

Steps to reproduce

1. Install Magento 2.1 RC1 via composer.
2. Compile DI or enable production mode.
   • 'php bin/magento setup:di:compile' or
   • 'php bin/magento deploy:mode:set production'
3. Run upgrade command (results in error)
   • 'php bin/magento setup:upgrade' or
   • 'php bin/magento setup:upgrade --keep-generated'

Expected result

1. For setup:upgrade to run and process necessary upgrades

Actual result

1. Upgrade does not run and results in error:

php bin/magento setup:upgrade --keep-generated

  [Exception]  
  Warning: file_get_contents(/Users/twolaver/magento/magento-rc1/var/di/setup.ser): failed to open stream: No such file or directory in /Users/twolaver/magento/magento-rc1/vendor/magento/framework/App/ObjectManager/ConfigLoader/Compiled.php on line 28              

Note: contents of var/di are:

• adminhtml.ser
• crontab.ser
• frontend.ser
• global.ser
• webapi_rest.ser
• webapi_soap.ser

[mazhalai]

@toddwolaver why would you run compile before upgrade? Also, if you are installing a fresh 2.1.0-rc1 why do you need to run upgrade? did you have an older code base?
Please follow the steps specified in the following link to upgrade: http://devdocs.magento.com/guides/v2.0/comp-mgr/cli/cli-upgrade.html

[toddwolaver]

@mazhalai The steps in this issue only illustrate the basic steps to recreate the error.

In a real world example, this would be run on a production deployment of an existing codebase. I run upgrade, compile DI and generate static assets off of the production server, move the updated codebase with generated files into place on production and re-run the upgrade with --keep-generated to update the production database. With the current error introduced in 2.1 RC1, this process is no longer viable.

[mazhalai]

@toddwolaver in this case, you will need to clear your var/generation and var/di manually before pushing to the server, since the previous generated files still exist and are no longer relevant since the code has been updated.

[toddwolaver]

@mazhalai Just to be clear, are you saying that in Magento 2.1 'setup:upgrade' will no longer be supported after DI has been compiled?

If so, I would recommend updating the error message and removing the --keep-generated option from setup:upgrade, since it now serves no purpose (i.e. to keep the previously generated files)

The process of building a production 'image' 'off site' minimizes the amount of processing needed in the production environment and limits need to put the production environment into maintenance mode during code deployments. The files are relevant since they were compiled against the updated codebase, just on a different server. However there is still need to update the production database after moving the production 'image' into place in the production environment, hence the need to run 'setup:upgrade --keep-generated' with the compiled files in place.

Thank you,
Todd

[mazhalai]

@toddwolaver No, what I mean is, setup:upgrade will not work with old generated code. We have a mechanism to clean this automatically before upgrade runs, but if you do this locally and push it, and run it with the --keep-generated flag, there is no way to clean the old code.

[toddwolaver]

Thank you @mazhalai

I still get an error when running 'php bin/magento setup:upgrade'. The only way to resolve the error is to manually remove var/di

Thank you,
Todd

php bin/magento setup:upgrade
                                                                                                                                                                
  [Exception]                                                                                                                                                   
  Warning: file_get_contents(/Users/twolaver/magento/magento-rc1/var/di/setup.ser): failed to open stream: No such file or directory in /Users/twolaver/magento/magento-rc1/vendor/magento/framework/App/ObjectManager/ConfigLoader/Compiled.php on line 28 

[mazhalai]

@toddwolaver what version were you on prior to rc1? Also, can you give us more info on your environment like web server, php version, etc.

[mazhalai]

@toddwolaver we have created ticket MAGETWO-53777 to investigate and fix.

[toddwolaver]

@mazhalai I had been using 2.0.7 prior to RC1

Environment details:

• Ubuntu 14.04.4 LTS
• PHP 5.6.19
• MySQL 5.6.28
• Apache 2.4.18

[peec]

Same problem here. ( 2.1-RC2 ) on production deploy. ( Development local copy works with no di compilation ).

Environment:

• PHP 7.0.4
• PHP-FPM with NGINX
• Mysql 5.6
• Magento 2.1-RC2

2.0.7 worked, upgraded to RC2 and now fails.

The commands i run:

echo "DI Compliation"
/src/bin/magento setup:di:compile  

echo "Setup upgrade"
/src/bin/magento setup:upgrade  /// THIS FAILS.

echo "Clearing cache"
/src/bin/magento cache:clean
/src/bin/magento cache:flush
/src/bin/magento setup:di:compile 

Log:

DI Compliation
Compilation was started.
%message% 0/7 [>---------------------------]   0% 1 sec 36.0 MiB%message% 0/7 [>---------------------------]   0% 1 sec 36.0 MiBProxies code generation... 0/7 [>---------------------------]   0% 1 sec 36.0 MiB
Proxies code generation... 1/7 [====>-----------------------]  14% 1 sec 40.0 MiB
Repositories code generation... 1/7 [====>-----------------------]  14% 1 sec 40.0 MiB
Repositories code generation... 2/7 [========>-------------------]  28% 33 secs 140.0 MiB
Service data attributes generation... 2/7 [========>-------------------]  28% 33 secs 140.0 MiB
Service data attributes generation... 3/7 [============>---------------]  42% 33 secs 140.0 MiB
Application code generator... 3/7 [============>---------------]  42% 33 secs 140.0 MiB
Application code generator... 4/7 [================>-----------]  57% 2 mins 158.0 MiB
Interceptors generation... 4/7 [================>-----------]  57% 2 mins 158.0 MiB
Interceptors generation... 5/7 [====================>-------]  71% 3 mins 174.0 MiB
Area configuration aggregation... 5/7 [====================>-------]  71% 3 mins 174.0 MiB
Area configuration aggregation... 6/7 [========================>---]  85% 4 mins 244.0 MiB
Interception cache generation... 6/7 [========================>---]  85% 4 mins 244.0 MiB
Interception cache generation... 7/7 [============================] 100% 4 mins 244.0 MiB
Generated code and dependency injection configuration successfully.
Setup upgrade



  [Exception]                                                                                                                                                                                  
  Warning: file_get_contents(/src/var/di/setup.ser): failed to open stream: No such file or directory in /src/vendor/magento/framework/App/ObjectManager/ConfigLoader/Compiled.php on line 28  



setup:upgrade [--keep-generated] [--magento-init-params="..."]

[davidalger]

@maksek @pboisvert This is a critical bug which I'm rather shocked was not addressed before the release of the GA for 2.1. It was reported nearly a month ago, and kills the ability to do fast atomic deployments of code either by capistrano, imaging, etc, etc.

When can we expect to see this fixed? All deployments via the capistrano-magento2 Gem are now busted, and there is not really a good workaround, as running setup:upgrade on a production server before setup:di:compile is run on the new code is not very feasible, as it would mean having a site in maintenance mode while the compilation (which takes ~3 min) runs.