-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
klarna-module-ordermanagement-4.1.3.0 checksum verification failed #16129
Comments
Am having the same issue attempting to upgrade |
Temporary if you don't need that module you can remove (replace) it by adding this to your composer.json
|
Just to be clear, a
|
Same issue for me, upgrading from 2.2.2 to 2.2.4. |
For us, the workaround mentioned here doesn't work: #16129 (comment) I receive this:
|
@careys7 Are you updating magento or making a fresh install? I was upgrading. (updated original comment) |
@quisse We have a running version of 2.2.4. |
@careys7 Can you check if the module is enabled somewhere? Here one of our team members updated magento in a project to 2.2.4 and i was pulling & installing the latest version of the project and adding that line & run composer install again solved the checksum issue... |
@quisse This workaround worked for me. I was doing a fresh install on a free trial. |
having the same issue |
Having same issue on Magento Cloud v 2.2.4 |
@quisse workaround worked for me aswell - if u dont use klarna... |
Can confirm this issue, having the same problem when trying to install 2.2.4. |
i had same issue, but now it seems to work again. |
I had the same issue, and after a composer update I got it working fine. |
The issue doesn't appear anymore for me neither, so i'll close this for now. |
Getting the same issue on Magento Cloud v 2.2.4 |
Have you tried flushing the composer cache? |
Getting the same issue on a Gitlab CI without composer cache Edit: The solution in comment #16129 (comment) does work for me. |
I can confirm that issue is back again without composer cache, the only working solution is in the comment made by @quisse |
The klarna/module-ordermanagement package was re-uploaded to the Marketplace (the package contents is the same, but file meta data differs, that's why the checksum has been changed). Magento has identified an issue and prevent it from happening this in the future, but now to solve it you have to run:
You can't update just a single package because it isn't in the require section, that's why you have to run |
@magento-engcom-team could you please mark this issue as solved? Thanks! |
@yyevgenii: if a package is re-uploaded and the hash changes it should always get a new version. The way this was handled right now is just bad management. Hope this won't happen anymore in the future... |
@hostep the team responsible for this has found the process in a workflow which may cause issue like this one. they said that it'll be reworked and the issue shouldn't happen again. |
Hi @yyevgenii , |
@mmenozzi, please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this issue. The GitHub issue tracker is intended for Magento Core technical issues only. |
The issue occured today in my Magento Commerce 2.2.5 installation. |
@engcom-backlog-pb this IS a Magento Core technical issue. |
@cmuench, please follow these guidelines for proper tracking of your issue. You can report Commerce-related issues in one of two ways: GitHub is intended for Magento Open Source users to report on issues related to Open Source only. |
@engcom-backlog-pb I created a ticket in the Enterprise Support. |
Enterprise support suggests:
In my case this solves the problem. |
@cmuench have you seen the same instruction in this thread? |
|
@quisse we always commit the composer.lock. It is only a hint for other ppl here. @yyevgenii yes, but we need this information in the release notes of Magento 2.2.5. This is an problem for all developer who update from 2.2.4. |
Just a little clarification about @cmuench commands:
If you run composer update you will update all packages, and sometimes maybe you don't want to.
So the `composer.lock' will be update with shasum correctly and you can download the package |
@giuseppemorelli it looks like the klarna/module-ordermanagement won't be updated with the |
@yyevgenii
|
Remove the composer.lock file and then run composer install again |
Preconditions
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: