Closed Jens-Bourgeois closed 4 years ago
Thanks for opening this issue!
Hi @Jens-Bourgeois. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.
@Jens-Bourgeois do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Thanks for opening this issue!
Thanks for opening this issue!
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: :point_down:
[ ] 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
branchDetails
- 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.
Thanks for opening this issue!
:white_check_mark: Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-30969
were created
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
@magento give me 2.4-develop instance
Hi @gauravagarwal1001. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @gauravagarwal1001, here is your Magento instance.
Admin access: https://i-26590-2-4-develop.instances.magento-community.engineering/admin_b812
Login: 564fb5ee
Password: 89924c4d4a88
Instance will be terminated in up to 3 hours.
I am working on this issue at #MM20IN
@vignesvaran thank you for joining. Please accept team invitation here and self-assign the issue.
Hi @vignesvaran. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
[ ] 1. Add/Edit Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 2. Verify that the issue is reproducible on 2.4-develop
branchDetails
- 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!
[ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.
Hi @shikhamis11. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:
[ ] 1. Add/Edit Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 2. Verify that the issue is reproducible on 2.4-develop
branchDetails
- 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!
[ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.
@Jens-Bourgeois This has been fixed and pull request has been created https://github.com/magento/magento2/pull/26642
Great thx!
Hi @Jens-Bourgeois. Thank you for your report. The issue has been fixed in magento/magento2#26642 by @princecb in 2.4-develop branch Related commit(s):
The fix will be available with the upcoming 2.4.0 release.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
Exception message in var/log system.log:
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'XXX' for key 'CUSTOMER_ENTITY_EMAIL_WEBSITE_ID', query was: INSERT INTO
customer_entity
(website_id
,email
,group_id
,store_id
,created_at
,updated_at
,disable_auto_group_change
,created_in
,firstname
,lastname
,password_hash
,taxvat
,confirmation
) VALUES (?, ?, ?, ?, '2020-01-23 12:39:15', '2020-01-23 12:39:15', ?, ?, ?, ?, ?, ?, ?) Trace: