M2.1.0: System Upgrade: Component Dependency throws error, does not give any details.

[apurv-anand]

M2.1.0: System Upgrade: Component Dependency throws error, does not give any details.

This issue occurred again while upgrading M2.1.0 to M2.1.1

The upgrade triggered from admin interface fails at component dependency. The error does not give any clue which component is facing the issue. No logs (at least I am not able to locate it) has the details.

Steps:

• Login to M2.1.0 backend.
• Go to System Upgrade.
• Check that 2.1.1 is available.
• Start the upgrade.

The system fails on dependency failure with no clue to user what should be fixed.

Expected: Clear details for the error so that user can take right actions. I am not sure which log would have the details. The log details can be mentioned in the comment for us to move forward as a workaround.

[alex-code]

I've encountered this before, the fix for me was to increase the memory limit in PHP.

[apurv-anand]

We have increased the memory limit to 2GB. The issue still exist. Any other pointers to resolve the issue? I am not even sure what the issue is. How do we reach that information first?

[apurv-anand]

Guys, any leads on how to debug this issue? If I know which module has the problem, I can try solving it...but how to figure out which one has the issue? Let me know if there are logs that I am missing to look at currently. This is urgent.

[UKRogue]

Exactly the same problem here and same versions. Memory increase has no affect. Is there anyone out there who can help us move past this problem?

[apurv-anand]

Developers, we need attention on this, or at-least a workaround. Don't have any clue what the problem is, so cannot resolve it. Please take this up on priority.

[shiftedreality]

Hi @apurv-anand

Please provide more details about your environment: OS version, PHP version, Apache/Nginx

[apurv-anand]

OS version: Ubuntu 14.04.4 LTS
PHP: PHP 7.0.9 (Zend Engine: v3.0.0.)
Apache: Apache/2.4.23

[shiftedreality]

@apurv-anand

Could you please also try next approach:

• Go to Readiness check where error is happening
• Open Developer Console
• Go to tab XHR
• Press Try Again button
• Observe action called "componentDependency"
• Provide response that it gives to you