Cannot instantiate interface Magento\ServicesId\Model\ServicesConfigInterface

j2vos commented 3 days ago

Preconditions and environment

Hello,

I am currently on the migration from 2.4.6p2 to 2.4.7p3 and during a setup:upgrade I get this error message:

Module 'Magento_ServicesId': 
2024-11-19T15:10:39.287144308Z 2024-11-19T15:10:39.287157301Z There is an error in /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php at line: 50 2024-11-19T15:10:39.287160569Z Cannot instantiate interface Magento\ServicesId\Model\ServicesConfigInterface#0 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(73): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create() 
2024-11-19T15:10:39.287165109Z #1 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(170): Magento\Framework\Ob
jectManager\ObjectManager->get() 
2024-11-19T15:10:39.287167809Z #2 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(276): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument() 2024-11-19T15:10:39.287170497Z #3 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(239): Magento\Framework\ObjectManager\Factory\AbstractFactory->getResolvedArgument() 2024-11-19T15:10:39.287173150Z #4 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime() 
2024-11-19T15:10:39.287175785Z #5 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments() 2024-11-19T15:10:39.287178396Z #6 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create() 2024-11-19T15:10:39.287180987Z #7 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(1250): Magento\Framework\ObjectManager\ObjectManager->create() 
2024-11-19T15:10:39.287183505Z #8 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(1668): Magento\Setup\Model\Installer->createSchemaDataHandler() 
2024-11-19T15:10:39.287186019Z #9 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(1114): Magento\Setup\Model\Installer->getSchemaDataHandler() 
2024-11-19T15:10:39.287188550Z #10 /var/www/html/setup/src/Magento/Setup/Model/Installer.php(966): Magento\Setup\Model\Installer->handleDBSchemaData() 
2024-11-19T15:10:39.287191047Z #11 /var/www/html/setup/src/Magento/Setup/Console/Command/UpgradeCommand.php(149): Magento\Setup\Model\Installer->installDataFixtures() 
2024-11-19T15:10:39.287194156Z #12 /var/www/html/vendor/symfony/console/Command/Command.php(326): Magento\Setup\Console\Command\UpgradeCommand->execute() 
2024-11-19T15:10:39.287204791Z #13 /var/www/html/vendor/symfony/console/Application.php(1078): Sy
mfony\Component\Console\Command\Command->run() 
2024-11-19T15:10:39.287207805Z #14 /var/www/html/vendor/symfony/console/Application.php(324): Symfony\Component\Console\Application->doRunCommand() 
2024-11-19T15:10:39.287210440Z #15 /var/www/html/vendor/magento/framework/Console/Cli.php(118): Symfony\Component\Console\Application->doRun() 
2024-11-19T15:10:39.287212960Z #16 /var/www/html/vendor/symfony/console/Application.php(175): Magento\Framework\Console\Cli->doRun() 
2024-11-19T15:10:39.287215461Z #17 /var/www/html/bin/magento(23): Symfony\Component\Console\Application->run()

The module vendor is present, it is not disabled by the config.php

The Magento_Config and Magento_ServicesConnector dependencies are also present and not disabled.

I can't understand why, I'm a bit stuck, if you have any ideas.

Steps to reproduce

php bin/magento se:up

Expected result

Setup upgrade

Actual result

Setup upgrade KO

Additional information

No response

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 3 days ago

Hi @j2vos. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

m2-assistant[bot] commented 2 days ago

Hi @engcom-Delta. 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: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
[ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Delta commented 2 days ago

Hi @j2vos ,

Thanks for your reporting and collaboration. We have verified the issue in 2.4.6p2 to 2.4.7p3 version, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

Upgrade from 2.4.6p2 to 2.4.7p3
Run php bin/magento setup:upgrade
Observe user is able to run setup upgrade without error

Can you please re-verify and confirm if you are still facing the issue. Thanks.

magento / magento2