cancel
Showing results for 
Search instead for 
Did you mean: 

Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin policy)

SOLVED

Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin policy)

Hi,

 

I just submitted an extension that works on Magento 2.3 and 2.4.
The automatic Varnish test failed on 2.3 but I am pretty sure this is not on my side.
The report json end with something like this (I had to truncate):

"Finished with the \"1\" exit code. Process output:Updating to version 2.3.3 (stable channel).Cleaning directories:Cleaning setup directory.Cleaning vendor directory.Cleaning generated directory.Removing app/etc/env.php fileInstalling dependencies.Starting schema dist file generationDist file was successfully generated: /app/.magento.env.mdRunning \"build\" hook.[2022-07-05 07:18:00] INFO: Starting scenario(s): scenario/build/generate.xml (magento/ece-tools version: 2002.1.10, magento/magento2-base version: 2.3.7-p3)[2022-07-05 07:18:01] INFO: Verbosity level is not set[2022-07-05 07:18:01] NOTICE: Applying patches[2022-07-05 07:18:01] NOTICE: End of applying patches[2022-07-05 07:18:01] INFO: Set Magento application mode to 'production'[2022-07-05 07:18:01] NOTICE: Validating configuration[2022-07-05 07:18:01] NOTICE: Fix configuration with given suggestions:[2022-07-05 07:18:01] WARNING: [1006] The configured state is not idealNo stores/website/locales found in config.php To speed up the deploy process do the following: 1. Using SSH, log in to your Magento Cloud account 2. Run \"php ./vendor/bin/ece-tools config:dump\" 3. Using SCP, copy the app/etc/config.php file to your local repository 4. Add, commit, and push your changes to the app/etc/config.php file[2022-07-05 07:18:01] NOTICE: End of validation[2022-07-05 07:18:01] NOTICE: Reconciling installed modules with shared config.[2022-07-05 07:18:01] ERROR: [11] The command \"php ./bin/magento module:enable --all --ansi --no-interaction\" failed. Warning: require(/app/setup/config/application.config.php): failed to open stream: No such file or directory in /app/vendor/magento/framework/Console/Cli.php on line 78returned non-zero exit status 11Creating magento_build_run ... \r\u001B[1A\u001B[2K\rCreating magento_build_run ... \u001B[32mdone\u001B[0m\r\u001B[1BYou are running composer as \"root\", while \"/composer\" is owned by \"www\" Downloading (connecting...)\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\bDownloading (100%) \b\b\b\b\b\b\b\b\bUse composer self-update --rollback to return to version 1.10.22You are using the deprecated option \"--no-suggest\". It has no effect and will break in Composer 3.Installing dependencies from lock file (including require-dev)Verifying lock file contents can be installed on current platform.Package operations: 476 installs, 0 updates, 0 removals - Installing cweagans/composer-patches (1.7.2): Extracting archivecweagans/composer-patches contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. See https://getcomposer.org/allow-pluginsYou can run \"composer config --no-plugins allow-plugins.cweagans/composer-patches [true|false]\" to enable it (true) or keep it disabled and suppress this warning (false) - Installing laminas/laminas-dependency-plugin (2.2.0): Extracting archivelaminas/laminas-dependency-plugin contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. See https://getcomposer.org/allow-pluginsYou can run \"composer config --no-plugins allow-plugins.laminas/laminas-dependency-plugin [true|false]\" to enable it (true) or keep it disabled and suppress this warning (false) - Installing symfony/polyfill-php80 (v1.25.0): Extracting archive - Installing symfony/polyfill-mbstring (v1.25.0): Extracting archive - Installing symfony/deprecation-contracts (v2.5.1): Extracting archive - Installing symfony/polyfill-ctype (v1.25.0): Extracting archive - Installing wikimedia/less.php (1.8.2): Extracting archive - Installing tedivm/jshrink (v1.3.3): Extracting archive - Installing symfony/process (v4.4.40): Extracting archive - Installing psr/container (1.1.2): Extracting archive - Installing symfony/service-contracts (v2.5.1): Extracting archive - Installing symfony/polyfill-php73 (v1.25.0): Extracting archive - Installing symfony/console (v4.4.40): Extracting archive - Installing psr/log (1.1.4): Extracting archive - Installing monolog/monolog (1.27.0): Extracting archive - Installing magento/zendframework1 (1.14.5): Extracting archive - Installing laminas/laminas-stdlib (3.7.1): Extracting archive - Installing container-interop/container-interop (1.2.0): Extracting archive - Installing laminas/laminas-validator (2.17.0): Extracting archive - Installing laminas/laminas-zendframework-bridge (1.5.0): Extracting archive - Installing laminas/laminas-escaper (2.7.0): Extracting archive - Installing laminas/laminas-uri (2.8.1): Extracting archive - Installing laminas/laminas-servicemanager (2.7.11): Extracting archive - Installing psr/http-message (1.0.1): Extracting archive - Installing laminas/laminas-loader (2.8.0): Extracting archive - Installing laminas/laminas-http (2.14.3): Extracting archive - Installing laminas/laminas-diactoros (1.8.7p2): Extracting archive - Installing laminas/laminas-psr7bridge (0.2.2): Extracting archive - Installing laminas/laminas-hydrator (2.4.2): Extracting archive - Installing laminas/laminas-filter (2.14.0): Extracting archive - Installing laminas/laminas-inputfilter (2.10.1): Extracting archive - Installing laminas/laminas-form (2.15.1): Extracting archive - Installing laminas/laminas-eventmanager (3.5.0): Extracting archive - Installing laminas/laminas-console (2.8.0): Extracting archive - Installing laminas/laminas-mvc (2.7.15): Extracting archive - Installing laminas/laminas-mime (2.9.1): Extracting archive - Installing webmozart/assert (1.10.0): Extracting archive - Installing symfony/polyfill-php72 (v1.25.0): Extracting archive - Installing symfony/polyfill-intl-normalizer (v1.25.0): Extracting archive - Installing symfony/polyfill-intl-idn (v1.25.0): Extracting archive - Installing laminas/laminas-mail (2.16.0): Extracting archive - Installing laminas/laminas-math (2.7.1): Extracting archive - Installing laminas/laminas-crypt (2.6.0): Extracting archive - Installing laminas/laminas-code (3.4.1): Extracting archive - Installing ralouphie/getallheaders (3.0.3): Extracting archive - Installing guzzlehttp/psr7 (1.8.5): Extracting archive - Installing guzzlehttp/promises (1.5.1): Extracting archive - Installing guzzlehttp/guzzle (6.5.5): Extracting archive - Installing symfony/finder (v5.4.3): Extracting archive - Installing symfony/filesystem (v5.4.7): Extracting archive - Installing seld/phar-utils (1.2.0): Extracting archive - Installing seld/jsonlint (1.9.0): Extracting archive - Installing react/promise (v2.9.0): Extracting archive - Installing justinrainbow/json-schema (5.2.11): Extracting archive - Installing composer/pcre (1.0.1): Extracting archive - Installing composer/xdebug-handler (3.0.3): Extracting archive - Installing composer/spdx-licenses (1.5.6): Extracting archive - Installing composer/semver (3.3.2): Extracting archive - Installing composer/metadata-minifier (1.0.0): Extracting archive - Installing composer/ca-bundle (1.3.1): Extracting archive - Installing composer/composer (2.2.11): Extracting archive - Installing colinmollenhour/credis (1.11.1): Extracting archive - Installing colinmollenhour/php-redis-session-abstract (v1.4.5): Extracting archive - Installing magento/framework (102.0.7-p3): Extracting archive - Installing magento/magento-composer-installer (0.3.0): Extracting archivemagento/magento-composer-installer contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. See https://getcomposer.org/allow-pluginsYou can run \"composer config --no-plugins allow-plugins.magento/magento-composer-installer [true|false]\" to enable it (true) or keep it disabled and suppress this warning (false) -ule-cms-graph-ql (100.3.5): Extracting archive - Installing magento/module-checkout-agreements-graph-ql (100.3.2): Extracting archive - Installing magento/module-catalog-widget (100.3.7): Extracting archive - Installing magento/module-catalog-url-rewrite-graph-ql (100.3.6): Extracting archive - Installing magento/module-catalog-rule-graph-ql (100.3.1): Extracting archive - Installing magento/module-catalog-rule-configurable (100.3.6): Extracting archive - Installing magento/module-catalog-inventory-graph-ql (100.3.5): Extracting archive - Installing magento/module-catalog-customer-graph-ql (100.3.1): Extracting archive - Installing magento/module-catalog-cms-graph-ql (100.3.1): Extracting archive - Installing magento/module-catalog-analytics (100.3.5): Extracting archive - Installing magento/module-cardinal-commerce (100.3.3): Extracting archive - Installing magento/module-cache-invalidate (100.3.5): Extracting archive - Installing magento/module-bundle-import-export (100.3.6): Extracting archive - Installing magento/module-bundle-graph-ql (100.3.5): Extracting archive - Installing braintree/braintree_php (3.35.0): Extracting archive - Installing magento/module-braintree (100.3.7-p2): Extracting archive - Installing magento/module-braintree-graph-ql (100.3.4): Extracting archive - Installing magento/module-authorizenet-graph-ql (100.3.3): Extracting archive - Installing magento/module-authorizenet-acceptjs (100.3.5): Extracting archive - Installing magento/module-authorizenet-cardinal (100.3.2): Extracting archive - Installing magento/module-authorizenet (100.3.6): Extracting archive - Installing magento/framework-amqp (100.3.6): Extracting archive - Installing magento/module-amqp-store (100.3.2): Extracting archive - Installing magento/framework-message-queue (100.3.7): Extracting archive - Installing magento/module-amqp (100.3.5): Extracting archive - Installing magento/module-advanced-pricing-import-export (100.3.5): Extracting archive - Installing magento/module-admin-notification (100.3.6): Extracting archive - Installing magento/module-admin-analytics (100.3.3-p2): Extracting archive - Installing magento/composer (1.7.0): Extracting archive - Installing laminas/laminas-json (2.6.1): Extracting archive - Installing laminas/laminas-view (2.11.5): Extracting archive - Installing laminas/laminas-text (2.7.1): Extracting archive - Installing laminas/laminas-server (2.9.2): Extracting archive - Installing laminas/laminas-soap (2.9.0): Extracting archive - Installing laminas/laminas-serializer (2.10.0): Extracting archive - Installing webimpress/safe-writer (2.2.0): Extracting archive - Installing laminas/laminas-config (2.6.0): Extracting archive - Installing laminas/laminas-modulemanager (2.9.0): Extracting archive - Installing laminas/laminas-log (2.12.0): Extracting archive - Installing laminas/laminas-i18n (2.14.0): Extracting archive - Installing laminas/laminas-di (2.6.1): Extracting archive - Installing magento/magento2-base (2.3.7-p3): ... Use laminas/laminas-cli...: The command \"php ./bin/magento module:enable --all --ansi --no-interaction\" failed. Warning: require(/app/setup/config/application.config.php): failed to open stream: No such file or directory in /app/vendor/magento/framework /Console/Cli.php on line 78In Shell.php line 86:The command \"php ./bin/magento module:enable --all --ansi --no-interaction\" failed. Warning: require(/app/setup/config/application.config.php):..."

and I guess the issue is coming from the fact that composer 2 does not allow all plugin by default since the beginning of July 2022.

Thus, we have error like "Composer plugin which is blocked by your allow-plugins config" and it breaks all the installation process.


I received an email saying that I have to contact the support but I can not submit ticket anymore... Seems that it's now reserved for "entitled user".

So, I post here, just in case.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

I just saw on the Magento 2 slack that it has been fixed today.

 

Thanks

View solution in original post

8 REPLIES 8

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

Hey guys!

 

We are having the same problem to upload a new version with compatibility with Magento 2.4.4 and PHP 8.1.

 

Is there any prediction of normalization?

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

Yes we have the same problem!  I can't work out from the JSON what the problem is.  Anyone got any ideas?

 

We're also getting a Broken on AdminCreateOrderWithSimpleProductTest on MFTF Adobe Commerce Supplied with Magento Edition : ce, but not ee.  Our extension doesn't do anything with creating orders, so it's really puzzling!

 

The only text we have in the output that contains the word "broken" is:

 

The expected HTTP response code for an un-existent Magento URL page is 404, got $httpCode It could be because the FPM service is not ready yet or this Magento installation is broken

- do you think there is something up with their system?  FPM is part of the base PHP system, not something we can do anything with in our extension.

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

Just to complete my first post:

Magento 2.3.7 "Installation and Varnish" validation process is using composer 2.
Since the beginning of July 2022, the default behavior concerning allow-plugins configuration is to not allow any plugins : see here.

Thus, all necessary plugins like magento/magento-composer-installer, magento/composer-root-update-plugin are not loaded anymore, and it breaks the installation automated process.

Thanks

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

We have this problem as well on our latest upload to Marketplace


Specifically in the command:

docker-compose -f docker-compose.yml run --rm build cloud-build

We get this error:

The command \"php ./bin/magento module:enable --all --ansi --no-interaction\"  \n   failed. Warning: require(/app/setup/config/application.config.php): failed  \n   to open stream: No such file or directory in /app/vendor/magento/framework  \n  /Console/Cli.php on line 78  

 

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

If someone from the Adobe/Magento commerce team read this, here is a possible solution to update the installation process: https://github.com/composer/composer/issues/10928#issuecomment-1181534484

 

Thanks

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

I just saw on the Magento 2 slack that it has been fixed today.

 

Thanks

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

I opened a ticket with Magento support as well. Then got a mail about an hour ago saying that a run which had already failed the automated tests, had passed and was going into manual QA.

Re: Marketplace Installation & Varnish Test : failed for Magento 2.3.7 (composer allow-plugin p

Hello

 

Have you found a solution to this problem ?

 

We are facing the same issue, but we couldn't find a solution.

 

Json report doesn't contain any relevant information. We just have the following message : 

Installation & Varnish Test Results
Environment: PHP 8.2 Adobe Commerce 2.4.6-p3 ce
Environment: PHP 8.2 Adobe Commerce 2.4.6-p3 ee
 
Thanks in advance