SQL error on 2.4.4 prerelease when saving a product with new source and stock

[MargoKep]

Preconditions (*)

1. Magento 2.4.4 prerelease
2. PHP 8.1
3. Magento with prefix in DB

Steps to reproduce (*)
1.Create new source
2.Create new stock and assign for new source
4. Going to: Catalog-->Product--> Open random product, Assigning for new Source, add Q-ty
5. Push the Save button

Expected result (*)

1. Success after save wtihout error, and seeing on the Products Greed Q-ty >0 in column Stock

Actual result (*)

1. SQL Error and on the Products Grid in column Stock=0 and not displaying on FrontArea:
   https://imgur.com/a/Mj7vS0x https://imgur.com/a/POWJtKH
   SQLSTATE[42S02]: Base table or view not found: 1146 Table 'docker_mg244eegolaya.pref_reservations_temp_for_stock_2' doesn't exist, query was: SELECT source_item.sku, SUM(IF(source_item.status = 0, 0, source_item.quantity)) AS quantity, IF((reservations.reservation_qty IS NULL OR (SUM(source_item.quantity) + reservations.reservation_qty) > 0) AND (((legacy_stock_item.use_config_backorders = 0 AND legacy_stock_item.backorders <> 0) AND (legacy_stock_item.min_qty >= 0 OR legacy_stock_item.qty > legacy_stock_item.min_qty) AND SUM(IF(source_item.status = 0, 0, 1))) OR ((legacy_stock_item.use_config_manage_stock = 0 AND legacy_stock_item.manage_stock = 0)) OR ((legacy_stock_item.use_config_min_qty = 1 AND SUM(IF(source_item.status = 0, 0, source_item.quantity)) > 0) OR (legacy_stock_item.use_config_min_qty = 0 AND SUM(IF(source_item.status = 0, 0, source_item.quantity)) > legacy_stock_item.min_qty)) OR (product.sku IS NULL)), 1, 0) AS is_salable FROM pref_inventory_source_item AS source_item LEFT JOIN pref_catalog_product_entity AS product ON product.sku = source_item.sku AND (product.created_in <= 1 AND product.updated_in > 1) LEFT JOIN pref_cataloginventory_stock_item AS legacy_stock_item ON product.entity_id = legacy_stock_item.product_id LEFT JOIN pref_reservations_temp_for_stock_2 AS reservations ON source_item.sku = reservations.sku WHERE (source_item.source_code IN ('a2')) AND (source_item.sku IN ('24-MB01')) GROUP BY source_item.sku

Severity (*) S0

[m2-assistant]

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

[m2-assistant]

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

[MargoKep]

Update Precondition:
3. Magento with prefix in DB

[awkomarov]

The issue was caused by DB prefix. Temporary table "reservations_temp_for_stock_" created without DB prefix. As a soultion I created solution, see attached diff
fix.txt

[engcom-Delta]

Hi @MargoKep ,
Thank you for raising an issue , We tried to reproduce the issue on Magento 2.4.3-p1 instance , in fact we are not able to reproduce same error , getting different error. Hence request to review the provided steps.
Actual results: "The stock item was unable to be saved. Please try again."

Test Results screenshots:

[MargoKep]

engcom-Delta

Precondition: Version Magento-2.4.4 prerelease!!! NOT 2.4.3
@engcom-Delta engcom-Delta

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