Random Error while waiting for package deployed

[talset]

Preconditions (*)

1. Magento version: 2.2.8

2. Magento source code is build by concourse (https://concourse-ci.org/).
   The concourse task use a docker image based on php:7.1 with composer and few tools added.

3. "Build" steps:

composer install -o -q --ignore-platform-reqs
php -d memory_limit=2048M bin/magento setup:di:compile
rm -Rf var/composer_home var/log var/page_cache var/session
rm -Rf 'pub/static/adminhtml/*'
rm -Rf 'pub/static/frontend/*'
rm -Rf 'var/view_preprocessed/pub/*'
CONFIG__DEFAULT__DEV__JS__MINIFY_FILES=1
MAGE_MODE=production
php -d memory_limit=2048M bin/magento setup:static-content:deploy -f --exclude-theme=Magento/backend --jobs=4 fr_FR

Steps to reproduce (*)

1. The issue seems quite random but ot happen with the following command php -d memory_limit=2048M bin/magento setup:static-content:deploy -f --exclude-theme=Magento/backend --jobs=4 fr_FR

Expected result (*)

1. Not error returned by magento setup:static-content:deploy

Actual result (*)

php -d memory_limit=2048M bin/magento setup:static-content:deploy -f --exclude-theme=Magento/backend --jobs=4 fr_FR

Deploy using quick strategy
frontend/Magento/blank/fr_FR            2986/2986           ============================ 100% %  36 secs             
frontend/Magento/luma/fr_FR             3002/3002           ============================ 100% %  36 secs             
...
                                                          
 [RuntimeException]                                       
 Error while waiting for package deployed: 67; Status: 0  

setup:static-content:deploy [-f|--force] [-s|--strategy [STRATEGY]] [-a|--area [AREA]] [--exclude-area [EXCLUDE-AREA]] [-t|--theme [THEME]] [--exclude-theme [EXCLUDE-THEME]] [-l|--language [LANGUAGE]] [--exclude-language [EXCLUDE-LANGUAGE]] [-j|--jobs [JOBS]] [--symlink-locale] [--content-version CONTENT-VERSION] [--refresh-content-version-only] [--no-javascript] [--no-css] [--no-less] [--no-images] [--no-fonts] [--no-html] [--no-misc] [--no-html-minify] [--] [<languages>]...

The issue is really random, we have 3 environments (dev/staging/prod) and it happen randomly once a day or less. After the issue if we run the same build pipeline it works.

Do you have any idea of what does it means ? What could be the issue ?

[magento-engcom-team]

Hi @talset. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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: 👇

• 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

Hi @talset thank you for you report, but i'm not able to reproduce this on my local environment, your error comes from ->

Please try debug at this point and let me know result, because we cannot accept random bugs :) thanks for collaboration 👍

[geerlingguy]

I get this error here and there when doing updates; note that my static content is in an NFS filesystem in production, so it is a little slow to read/write during static content deploy and setup:update. Just putting this out there, as I see it pop up in logs here and there, for no rhyme or reason. Usually the commands where I see it appear still work fine and complete though.

[ipascual]

Same issue happens randomly on Magento Cloud

[RuntimeException] Error while waiting for package deployed: 19104; Status: 0

which I know they have a network hard drive for pub/static

[ihor-sviziev]

Hi @engcom-backlog-nazar,
I have this issue too.

Did you tried to reproduce this issue inside docker on image php:7.1?

Hi @ihor-sviziev with php7.1 and without docker. i thinks this may be related to environment in cloud, did you have this issue on local environment ?

[CajuCLC]

This might be caused by this: https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Deploy/Process/Queue.php#L391

And the function for the timeout: https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Deploy/Process/Queue.php#L372

And that all goes to const DEFAULT_MAX_EXEC_TIME = 400;
https://github.com/magento/magento2/blob/2.3-develop/app/code/Magento/Deploy/Process/Queue.php#L32

So it looks like if the static code deploy runs for over 400 seconds, it will fail. Maybe increase this time or create an option in the admin where this can be set. If you are using NFS it might be slow to generated all themes or even some heavy themes. And it looks like that's what it was done to ECE: magento/ece-tools#418
We are using EFS and sometimes it fails, sometimes it doesn't.

[m2-assistant]

Hi @davidalger. 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: 👇

• 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.
  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x