magento2: klarna-module-ordermanagement-4.1.3.0 checksum verification failed

@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…

Temporary if you don’t need that module you can remove (replace) it by adding this to your composer.json I was updating the installation.

    "replace": {
        "klarna\/module-ordermanagement": "*"
    },

credits

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:

• composer clearcache
• rm -rf vendor/klarna/module-ordermanagement
• composer update

You can’t update just a single package because it isn’t in the require section, that’s why you have to run composer update. The version of the package remains the same, so composer won’t download it again, if the package is already installed, that’s why you have to remove the package from the vendor folder. Clear the composer cache just in case.

The issue occured today in my Magento Commerce 2.2.5 installation.

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

Just a little clarification about @cmuench commands:

composer clearcache
rm -rf vendor/klarna/module-ordermanagement
composer update

If you run composer update you will update all packages, and sometimes maybe you don’t want to. Just update the package with that has checksum error

composer clearcache
rm -rf vendor/klarna/module-ordermanagement
# update only the "broken package"
composer update klarna/module-ordermanagement

So the `composer.lock’ will be update with shasum correctly and you can download the package

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

composer.lock should always be commited.

@cmuench have you seen the same instruction in this thread? https://github.com/magento/magento2/issues/16129#issuecomment-400583192

I had the same issue, and after a composer update I got it working fine.

i had same issue, but now it seems to work again.