Upgrade from 2.1.9 to 2.2.0 - Check component dependendencies fails - no details

[mikeguy82]

So I have searched most of the internet for this but I could not find any help.

I am trying to upgrade from 2.1.9 to 2.2.0 and Check Component Dependency Fails.

Initially it failed because I had a module Eltrino_Region installed, but I have uninstalled the module to be able to upgrade using initially the "uninstall" in component manager, and that stopped with an error (forgot to copy error).

I removed Eltrino_Region with command prompt and it went through successfully.

I have flushed all caches.

I have ran the command below and Eltrino_Region is not listed in there anymore.

magento module:status

Now when I run the readiness check, it still says at the beginning while it's working, then eventually fails with no details:

If I try and upgrade using command line I get:

Your requirements could not be resolved to an installable set of packages.

Problem 1
- The requested package magento/product-community-edition could not be found in any version, there may be a typo in the package name.

Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting
see <...> for more details.

Summary:

Tried to upgrade to 2.2.0 from 2.1.9

Failed dependancy check because of a module I have installed called Eltrino_Region

Tried to uninstall module using the component manager ui, and got stuck on an error

Uninstalled Eltrino_Region with command line

Tried to upgrade to 2.2.0 again and still fail component readiness check.

Any help would be appreciated.

Thanks,

Mike

[Damian Culotta]

Hi @mikeguy82,

Which version of PHP you've tried to use with Magento 2.2?

Remember that PHP 5.x was dropped.

[mikeguy82]

Hi Damian,

Thanks for the reply. I have changed php version to 7, still get the similar failure.

Thanks,

Mike

[Damian Culotta]

Hi @mikeguy82,

Maybe you can take a look on your webserver error log?

Sometimes the error could be related with memory limit too. Can you check that?

[mikeguy82]

nothing showing in error logs and memory is set to 2gB already.

[RockMariska]

Hi @mikeguy82 @Damian Culotta,

I'm encountering same issue with dependency check. actually I'm trying to get around this for a week or so now and is driving me crazy.

I've tried to update from 2.1.9 to 2.2.0 and 2.2.1 with both I'm getting these issues.

Did you find a solution already?

[Rakesh Jesadiya]

@RockMariska @mikeguy82

For upgrade your version from older to latest, you can simply upgrade using below way,

Just open composer.json file from root of magento,

Replace two lines in composer.json file,

"version": "2.1.9",
"magento/product-community-edition": "2.1.9",

with your latest version,

"version": "2.2.1",
"magento/product-community-edition": "2.2.1",

Now save composer.json file,

Run command from root of magento system,

composer update

Now in 15-20 minute takes to upgrade your latest version.

if issue solved,Click kudos/Accept as solutions.

[mikeguy82]

{
    "name": "magento/project-community-edition",
    "description": "eCommerce Platform for Growth (Community Edition)",
    "type": "project",
    "version": "2.2.1",
    "license": [
        "OSL-3.0",
        "AFL-3.0"
    ],
    "require": {
        "magento/product-community-edition": "2.2.1",
        "composer/composer": "@alpha"
    },
    "require-dev": {
        "phpunit/phpunit": "4.1.0",
        "squizlabs/php_codesniffer": "1.5.3",
        "phpmd/phpmd": "@stable",
        "pdepend/pdepend": "2.4.0",
        "fabpot/php-cs-fixer": "~1.2",
        "lusitanian/oauth": "~0.3 <=0.7.0",
        "sebastian/phpcpd": "2.0.0"
    },
    "config": {
        "use-include-path": true
    },
    "autoload": {
        "psr-4": {
            "Magento\\Framework\\": "lib/internal/Magento/Framework/",
            "Magento\\Setup\\": "setup/src/Magento/Setup/",
            "Magento\\": "app/code/Magento/"
        },
        "psr-0": {
            "": "app/code/"
        },
        "files": [
            "app/etc/NonComposerComponentRegistration.php"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/",
            "Magento\\Tools\\": "dev/tools/Magento/Tools/",
            "Magento\\Tools\\Sanity\\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
            "Magento\\TestFramework\\Inspection\\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
            "Magento\\TestFramework\\Utility\\": "dev/tests/static/framework/Magento/TestFramework/Utility/"
        }
    },
    "minimum-stability": "alpha",
    "prefer-stable": true,
    "repositories": [
        {
            "type": "composer",
            "url": "https://repo.magento.com/"
        }
    ],
    "extra": {
        "magento-force": "override"
    }
}

@Rakesh Jesadiya above is what I changed the composer.json file in folder: /home/user/public_html/magento2

I have also changed the file in folder:/home/user/public_html/magento2/var to:

{
    "name": "magento/project-community-edition",
    "description": "eCommerce Platform for Growth (Community Edition)",
    "type": "project",
    "version": "2.2.1",
    "license": [
        "OSL-3.0",
        "AFL-3.0"
    ],
    "require": {
        "magento/product-community-edition": "2.2.1",
        "composer/composer": "@alpha"
    },
    "require-dev": {
        "phpunit/phpunit": "4.1.0",
        "squizlabs/php_codesniffer": "1.5.3",
        "phpmd/phpmd": "@stable",
        "pdepend/pdepend": "2.4.0",
        "fabpot/php-cs-fixer": "~1.2",
        "lusitanian/oauth": "~0.3 <=0.7.0",
        "sebastian/phpcpd": "2.0.0"
    },
    "config": {
        "use-include-path": true
    },
    "autoload": {
        "psr-4": {
            "Magento\\Framework\\": "lib/internal/Magento/Framework/",
            "Magento\\Setup\\": "setup/src/Magento/Setup/",
            "Magento\\": "app/code/Magento/"
        },
        "psr-0": {
            "": "app/code/"
        },
        "files": [
            "app/etc/NonComposerComponentRegistration.php"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/",
            "Magento\\Tools\\": "dev/tools/Magento/Tools/",
            "Magento\\Tools\\Sanity\\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
            "Magento\\TestFramework\\Inspection\\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
            "Magento\\TestFramework\\Utility\\": "dev/tests/static/framework/Magento/TestFramework/Utility/"
        }
    },
    "minimum-stability": "alpha",
    "prefer-stable": true,
    "repositories": [
        {
            "type": "composer",
            "url": "https://repo.magento.com/"
        }
    ],
    "extra": {
        "magento-force": "override"
    }
}

I am not sure if and what folder this composer.json should be modified but I modified both.

Last night I tried to run composer update with enterprise by mistake too, and now after modifying the files above as shown and running "composer update" I get the following: 

Do not run Composer as root/super user! See https://getcomposer.org/root for details
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package magento/product-community-edition could not be found in any version, there may be a typo in the package name.
  Problem 2
    - The requested package magento/product-enterprise-edition could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

[RockMariska]

Hi @Rakesh Jesadiya,

Thank you so much for your fast response. I've adjusted the composer.sjon like you suggested.

here's what happened next.

this is after composer update in SSH

this happened after magento setup upgrade, I've tried to module disable the ones that are mentioned but it seems I cannot do anything right now. When I ask module:list or module:status I only get the error messages back.

Thank you for your time and help!