Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From yesterday, issue after 'classic' composer update #35911

Closed
1 of 5 tasks
ghost opened this issue Aug 10, 2022 · 18 comments
Closed
1 of 5 tasks

From yesterday, issue after 'classic' composer update #35911

ghost opened this issue Aug 10, 2022 · 18 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response

Comments

@ghost
Copy link

ghost commented Aug 10, 2022

Preconditions and environment

  • Magento version 2.4.4
  • Anything else that would help a developer reproduce the bug

From yesterday, i can see a lot of module updated with simple composer update command.
I note that yesterday, magento 2.4.5 has released

I understand not why composer update make one upgrade of all magento core module without i specify require with Magento version.

Steps to reproduce

  • Magento version 2.4.4
  • Anything else that would help a developer reproduce the bug
    composer update
    bin/magento setup:upgrade
    bin/magento setup:di compile

Expected result

All working

Actual result

magento_user@achatpc:/var/www/html$ php bin/magento setup:upgrade
Cannot instantiate interface Magento\AdobeImsApi\Api\ConfigInterface#0 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create()
#1 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(170): Magento\Framework\ObjectManager\ObjectManager->get()
#2 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(276): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument()
#3 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(239): Magento\Framework\ObjectManager\Factory\AbstractFactory->getResolvedArgument()
#4 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime()
#5 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments()
#6 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create()
#7 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(170): Magento\Framework\ObjectManager\ObjectManager->get()
#8 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(276): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument()
#9 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(239): Magento\Framework\ObjectManager\Factory\AbstractFactory->getResolvedArgument()
#10 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime()
#11 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments()
#12 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create()
#13 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(170): Magento\Framework\ObjectManager\ObjectManager->get()
#14 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(276): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument()
#15 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(239): Magento\Framework\ObjectManager\Factory\AbstractFactory->getResolvedArgument()
#16 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime()
#17 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments()
#18 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(70): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create()
#19 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(206): Magento\Framework\ObjectManager\ObjectManager->get()
#20 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(182): Magento\Framework\ObjectManager\Factory\AbstractFactory->parseArray()
#21 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(276): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument()
#22 /var/www/html/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(239): Magento\Framework\ObjectManager\Factory\AbstractFactory->getResolvedArgument()
#23 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(34): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgumentsInRuntime()
#24 /var/www/html/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(59): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments()
#25 /var/www/html/vendor/magento/framework/ObjectManager/ObjectManager.php(56): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create()
#26 /var/www/html/vendor/magento/framework/Console/Cli.php(153): Magento\Framework\ObjectManager\ObjectManager->create()
#27 /var/www/html/vendor/magento/framework/Console/Cli.php(134): Magento\Framework\Console\Cli->getApplicationCommands()
#28 /var/www/html/vendor/symfony/console/Application.php(1274): Magento\Framework\Console\Cli->getDefaultCommands()
#29 /var/www/html/vendor/symfony/console/Application.php(629): Symfony\Component\Console\Application->init()
#30 /var/www/html/vendor/symfony/console/Application.php(237): Symfony\Component\Console\Application->find()
#31 /var/www/html/vendor/magento/framework/Console/Cli.php(115): Symfony\Component\Console\Application->doRun()
#32 /var/www/html/vendor/symfony/console/Application.php(149): Magento\Framework\Console\Cli->doRun()
#33 /var/www/html/bin/magento(23): Symfony\Component\Console\Application->run()
#34 {main}

Additional information

First bin/magento setup:upgrade working but after, any bin/magento commande provide this error.

Release note

No response

Triage and priority

  • 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
Copy link

m2-assistant bot commented Aug 10, 2022

Hi @achatpc. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@sdzhepa
Copy link
Contributor

sdzhepa commented Aug 10, 2022

Hello @achatpc

I am not sure but it looks like a known issue.
Could you please check this article and confirm if it helps?
https://support.magento.com/hc/en-us/articles/8214752983949

@ghost
Copy link
Author

ghost commented Aug 10, 2022

Hello,
Working for my production environement

Thank you so much!

@ghost ghost closed this as completed Aug 10, 2022
@ghost
Copy link
Author

ghost commented Aug 10, 2022

Well, I probably spoke a little fast...

On my developer environement:

This script allows you to stay on version 2.4.4 and to continue, if necessary, to run composer update and keep the versions of the different modules up to date.

However, after script rollback and update request to Magento 2.4.5, the issue reappears.

And the script does not work with Magento version 2.4.5.

Anyway, it is necessary to solve the initial error.

@m2-assistant
Copy link

m2-assistant bot commented Aug 11, 2022

Hi @engcom-Dash. 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).
      DetailsIf 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.
    1. 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.
    1. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - 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!

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label Aug 11, 2022
@engcom-Dash
Copy link
Contributor

Hi @achatpc ,

We are trying to reproduce the issue but we are not able to reproduce.
We are Expected results all working fine in magento 2.4.4 instance.

For reference here i attached the screenshots:
2
1

Steps to reproduce:
1.Install Magento 2.4.4 instance
2.Upgrade the instance
3.compile the instance
4. all working fine

Let us Know if we are miss anything....

Thanks!!!

@ghost
Copy link
Author

ghost commented Aug 11, 2022

Now try to upgrade to 2.4.5 version.

Can you provide me all uograde step ?

@johncy65
Copy link

I'm getting this error on 2.4.5

@engcom-Dash
Copy link
Contributor

Hi @achatpc ,

We got Same Result after updating the magento version 2.4.5

Here I attached Screenshots for your Reference...

Screenshot from 2022-08-12 16-11-10
Screenshot from 2022-08-12 16-10-57
Screenshot from 2022-08-12 16-10-51

Steps to Reproduce:
1.Install Magento 2.4.4 instance
2.Upgrade the instance --- "composer require magento/product-community-edition 2.4.5 --no-update"
3.Update the Composer ---- "composer update"
4.Compile the Instance -- "bin/magento setup:di:compile"
5. all working fine

Let us Know if We are Missing anything...

Thanks!!!

@devprofun
Copy link

Please check in app/etc/config.php if modules Magento_AdobeIms and Magento_AdobeImsApi are enabled.
I had the same problem, but it worked after enabling both modules and cleaning cache directory manually.

@johncy65
Copy link

Turns out it had to do something with Redis. After running redis-cli flushall it worked.

@ghost ghost closed this as completed Aug 12, 2022
@ghost
Copy link
Author

ghost commented Aug 12, 2022

Please check in app/etc/config.php if modules Magento_AdobeIms and Magento_AdobeImsApi are enabled. I had the same problem, but it worked after enabling both modules and cleaning cache directory manually.

Hello, thank you, this fix issue!

@Viktorja1
Copy link

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @Viktorja1. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@Rusllana
Copy link

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @Rusllana. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response
Projects
None yet
Development

No branches or pull requests

6 participants