Migration Tool conflict with 2.4.4 (Monolog)

[mbitson]

Unable to install the prerelease of Magento 2.4.4 while the Data Migration Tool is installed due to conflicting Monolog packages.

Preconditions (*)

1. Magento 2.4.3 installed
2. magento/data-migration-tool (latest, 2.4.3) installed
3. composer access to prerelease of 2.4.4

Steps to reproduce (*)

1. composer require-commerce magento/product-community-edition 2.4.4 --no-update --interactive-root-conflicts
2. composer update

Expected result (*)

1. Dependencies should resolve and Magento 2.4.4 and its dependencies should be installed.

Actual result (*)

  Problem 1
    - Root composer.json requires magento/data-migration-tool ^2.4 -> satisfiable by magento/data-migration-tool[2.4.0, 2.4.1, 2.4.2, 2.4.3].
    - magento/product-community-edition 2.4.4 requires monolog/monolog ^2.3 -> satisfiable by monolog/monolog[2.3.0, ..., 2.4.0].
    - You can only install one version of a package, so only one of these can be installed: monolog/monolog[1.0.0, ..., 1.27.0, 2.0.0, ..., 2.4.0].
    - magento/product-enterprise-edition 2.4.4 requires magento/product-community-edition 2.4.4 -> satisfiable by magento/product-community-edition[2.4.4].
    - magento/data-migration-tool[2.4.0, ..., 2.4.3] require monolog/monolog ^1.17 -> satisfiable by monolog/monolog[1.17.0, ..., 1.27.0].
    - Root composer.json requires magento/product-enterprise-edition 2.4.4 -> satisfiable by magento/product-enterprise-edition[2.4.4].

References

1. First, upgrade process for above was obtained from the Adobe doc here.
2. This was caused in this Pull Request, while this Issue was being addressed.
3. To resolve, data-migration-tool will need to update to Monolog ^2. A Monolog-written guide on that can be found here.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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]

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

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ 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

[hostep]

This one can be closed, see this comment in the duplicated issue that got created.

[m2-assistant]

Hi @engcom-Hotel. 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).

  Details

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

• 2. 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.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. 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!

• 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-Hotel]

Hello @mbitson,

We have tried to reproduce the issue in Magento 2.4.4 with the following steps:

1. Install Magento 2.4.3 by following this link.
2. Install the data-migration-tool by running the below command:
   composer require magento/data-migration-tool:2.4.3
3. Follow this link to upgrade the Magento with 2.4.4.
4. We are facing the below issue:
   

It seems either the issue is not fixed or it is not merged yet. Hence confirming the issue.

Thanks

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.magento.com/browse/AC-2871 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sdzhepa]

Hello @engcom-Hotel and @mbitson

Thank you for your report and collaboration!

Based on the comment from @hostep #35280 (comment) with reference to

The dependency issue was fixed in the latest Data Migration Tool 2.4.4

Could you please check this flow with the new version of Data Migration Tool 2.4.4 and confirm that issue is fixed?

Thank you in advance!

[engcom-Hotel]

Sure @sdzhepa

[engcom-Hotel]

Hello @mbitson @hostep @sdzhepa,

We have tried again to reproduce the issue but we are facing other problems. We have followed the below steps in order to reproduce the issue:

1. Install Magento 2.4.3
2. Trying to install data-migration-tool by running this command composer require magento/data-migration-tool:2.4.4, but whenever I am running this command, I am getting the below error:

As per the document, we need to use the same version, as Magento. So in this case I then tried composer require magento/data-migration-tool:2.4.3 which works fine. But after following the upgrading steps, I end up with the same error as I mentioned in this comment.

Please let us know if we have missed anything here.

Thanks

[hostep]

@engcom-Hotel: it was already confirmed that this issue is fixed in version 2.4.4 of the data migration tool.

So please don't waste time and don't try to reproduce this issue anymore because it has already been fixed. This issue (and the duplicated one) should just get closed :)

[victor-v-rad]

Hi @engcom-Hotel
Your Magneto composer.json probably has fixed DMT version, e.g.:
"magento/data-migration-tool": "2.4.3"
please change it to something like
"magento/data-migration-tool": "~2.4.3"
and repeat the composer update command

[engcom-Hotel]

Hello @victor-v-rad,

Thanks for the information!

I followed your comment and successfully upgrade the Magento from 2.4.3 to 2.4.4. Please refer to the screenshots below:

On 2.4.3 Version

After Upgrading with 2.4.4

I have made the changes as per your comment and the upgrade has been done successfully.

@mbitson Hence the issue has been resolved, can we close this issue?

Thanks

[engcom-Hotel]

Dear @mbitson,

We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards