Error while installing sample data in magento 2.4.1

[ajmalbuffy]

Preconditions:
Getting the below error while trying to install sample data and upgrading the setup in Magento 2.4.1
Error: Unable to apply data patch Magento\CatalogRuleSampleData\Setup\Patch\Data\InstallCatalogRuleSampleData for module Magento_CatalogRuleSampleData. Original exception message: Rolled back transaction has not been completed correctly.

Steps to reproduce:
Step:1 Install Magento 2.4.1 using composer and CLI
Step:2 Set to developer mode and run the sample data deploy and setup upgrade command
Commands used:
bin/magento sampledata:deploy
bin/magento setup:upgrade

Expected result:
setup:upgrade should be successful without any error and the site should be loaded with the sample data.

Actual result:
Getting the below error while trying to upgrade the setup after deploying the sample data.
Error: Unable to apply data patch Magento\CatalogRuleSampleData\Setup\Patch\Data\InstallCatalogRuleSampleData for module Magento_CatalogRuleSampleData. Original exception message: Rolled back transaction has not been completed correctly.

Environment details: I am using
ubuntu 20.04
PHP 7.3.25
apache 2.4.46
MYSQL 5.7.32
elastic search 7.6.0
Magento 2.4.1
composer 1.10.19

Recently I have installed the Magento 2.4.1 community edition in Ubuntu 20.04, Installation went correct and while I try to set sample data I got the error "Unable to apply data patch Magento\CatalogRuleSampleData\Setup\Patch\Data\InstallCatalogRuleSampleData for module Magento_CatalogRuleSampleData. Original exception message: Rolled back transaction has not been completed correctly."

I have searched about this issue and tried all the solution which have been provided

Tried solutions:

1. Switch to developer mode before installing sample data
2. Using MySQL 5.7
3. Remove the sample data and rerun again
4. Remove the corn job before installing the sample data but none of the solutions worked for me.
   

As a temporary fix, I have disabled the Magento_CatalogRuleSampleData Magento_SalesRuleSampleData and using the local site.

Anybody, please suggest a proper fix for this issue.

[m2-assistant]

Hi @ajmalbuffy. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

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

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[mrtuvn]

Have you try switch php version from 7.3 to 7.4( Ex: 7.4.9)

[mrtuvn]

Another problem come from
https://github.com/magento/magento2-sample-data/blob/2.4-develop/app/code/Magento/CatalogRuleSampleData/fixtures/catalog_rules.csv
Invalid json in csv in column conditions_serialized. As my view in code magento try to process string replace data before insert to database. You can see reference with %url_key=%
Before i still get issue similiar you but recently i don't get this issue anymore. Maybe this fixed or something else

[m2-assistant]

Hi @engcom-Bravo. 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-Bravo]

Hello @ajmalbuffy

Thank you for your report.

This is a known issue and has been previously reported, #30685 Here is the PR wich fixes the issue #30928
It will be fixed in the next release.

We are closing this issue as Duplicate of #30685

[moloni-es]

I have my Magento installation updated to the latest available version.
How can I apply this patch to make the sample data work in 2.4.1?

[unic0rn]

Hello @ajmalbuffy

Thank you for your report.

This is a known issue and has been previously reported, #30685 Here is the PR wich fixes the issue #30928
It will be fixed in the next release.

We are closing this issue as Duplicate of #30685

Unfortunately, I was getting the same error with the latest Magento release (as well as github clone). Disabling GTIDs in mysql fixed it.

[unic0rn]

Since someone found the above funny, here's the exact error from system.log:

[2021-02-13 00:11:43] main.ERROR: Sample Data error: SQLSTATE[HY000]: General error: 1787 Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions., query was: CREATE TEMPORARY TABLE tmp_select_RJittlP0DAn81zsDeB6aLI5XAtLrFjNF (PRIMARY KEY(url_rewrite_id),INDEX HASHKEY_ENTITY_STORE USING HASH(hash_key),INDEX ENTITY_STORE USING HASH(entity_id,store_id)) ENGINE=INNODB IGNORE (SELECT e.*, CONCAT(e.store_id,'_', e.entity_id) AS hash_key FROM url_rewrite AS e WHERE (entity_type = 'category') AND (entity_id IN('3'))) [] []

End result is the same error message as mentioned earlier here. Fresh install with GTIDs disabled works fine, but that's obviously just an ugly workaround. Looks like a different issue, just causing the same error from install script - and with people not posting exact system.log errors, the result is people looking for a solution find an old issue like this one, think it is fixed, but in reality they're encountering different bug. It's why I've posted about it here, mentioning "the same error", not "the same issue". I may open a new issue later on, for now I don't have time to replicate it to paste proper logs.

[mrtuvn]

https://devdocs.magento.com/guides/v2.4/install-gde/prereq/mysql.html
Maybe is not a bug this is feature LOLs

[vuhoi292]

I did had such a problem and recovered by run command
php bin/magento sampledata:remove
after upgrade run normally