Closed makkoff closed 1 year ago
Hi @makkoff. Thank you for your report. To speed up processing of this issue, 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@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @makkoff,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4.6 cloud instance and the issue is not reproducible.Kindly refer the attached video.
Steps to reproduce
We are able to place the order successfully.
https://github.com/magento/magento2/assets/51680745/436c8aac-1cf4-48a6-bc12-f7d845219542
Kindly recheck the behaviour on Magento 2.4.6 cloud instance and elaborate steps to reproduce if the issue is still reproducible.
Thanks.
Hi @makkoff,
Kindly provide us latest update on this https://github.com/magento/magento2/issues/37559#issuecomment-1587220412 you are able to reproduce the issue or still working on this issue and also please let us know if we are missing anything.
Thanks.
Hi @makkoff,
We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.
Thanks.
Preconditions and environment
Steps to reproduce
Note: Can reproduce this issue only at magneto cloud staging environment since there we use slave connection to the DB.
Expected result
The order was placed and the
inventory.reservations.updateSalabilityStatus
queue was successfully addedActual result
Getting the error:
the
inventory.reservations.updateSalabilityStatus
queue fails because the\Magento\MysqlMq\Model\ResourceModel\Queue::saveMessage
returns 0 instead of the last insert id(message id).I added a rewrite for
Magento\ResourceConnections\DB\Adapter\Pdo\MysqlProxy
to log the last insert IDs of slave and master connections:And here is the result:
[2023-05-30T12:47:36.737265+00:00] db_queue_logger.DEBUG: CONNECTIONS LOG: [] [] [2023-05-30T12:47:36.737307+00:00] db_queue_logger.DEBUG: MASTER Connection last insert ID - 9312 [] [] [2023-05-30T12:47:36.737347+00:00] db_queue_logger.DEBUG: MASTER Connection last insert ID with "queue" table - 9312 [] [] [2023-05-30T12:47:36.737387+00:00] db_queue_logger.DEBUG: SLAVE Connection last insert ID - 0 [] [] [2023-05-30T12:47:36.737425+00:00] db_queue_logger.DEBUG: SLAVE Connection last insert ID with "queue" table - 0
Additional information
DB query log: ...
...
Release note
This part of code was changed in 2.4.6
\Magento\ResourceConnections\DB\Adapter\Pdo\MysqlProxy::selectConnection
Triage and priority