Cannot add product in admin if single store mode website id != 1

[kyegil]

I'm not able to add any products from admin. My Magento is in single store mode with website id = 2.
Saving a new product fails with Integrity constraint violation.
Editing and saving an existing product works fine. I am also able to create new products using the import feature.
The issue was reproduced on a clean Magento instance.

Preconditions (*)

1. Magento Open Source 2.4.3-p1
2. php 7.4
3. MariaDB 10.4

Steps to reproduce (*)

1. Install a clean version of Magento version 2.4.3-p1
2. Add a new website, store and store view, and make this the default

• In Stores -> All Stores:

  • Create new website (new_website)
  • Create new store (new_store) under new_website
  • Create new store view (new_store_view) under new_store

• Open new_website again, and set this as default. Save.

3. Delete the preinstalled website (base)

4. Verify your website db entries. The default website should be 2:

   SELECT * FROM store_website;
   +------------+-------------+-------------+------------+------------------+------------+
   | website_id | code        | name        | sort_order | default_group_id | is_default |
   +------------+-------------+-------------+------------+------------------+------------+
   |          0 | admin       | Admin       |          0 |                0 |          0 |
   |          2 | new_website | New Website |          0 |                2 |          1 |
   +------------+-------------+-------------+------------+------------------+------------+
   
   

5. In Stores -> Configuration -> General -> SIngle-Store Mode

• Enable Single-store Mode. Save.

6. Verify your Single-store configuration:

   bin/magento config:show general/single_store_mode/enabled
   

   Should return 1

7. In Catalog -> Products

• Add Product
• Populate name, sku and price. Save.

Expected result (*)

1. The product should save successfully

Actual result (*)

1. The save action fails, with the following message:

`SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`denuhabsxr`.`catalog_product_website`, CONSTRAINT `CATALOG_PRODUCT_WEBSITE_WEBSITE_ID_STORE_WEBSITE_WEBSITE_ID` FOREIGN KEY (`website_id`) REFERENCES `store_website` (`website_id`) ON DELETE ), query was: INSERT INTO `catalog_product_website` (`product_id`,`website_id`) VALUES (?, ?)`

[m2-assistant]

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

🎥 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

[m2-assistant]

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

Hi @kyegil,

Thank you for reporting the issue.

I have tried this issue on the fresh installation (Magento 2.4-dev/2.4.3-P1) but I am not able to reproduce it. Product is created successfully with above steps followed
Kindly recheck the issue on Magento 2.4-develop branch and elaborate the steps if the issue is still reproducible.
Thank you.

[kyegil]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @kyegil. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @kyegil, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[kyegil]

@engcom-November Could you verify your website settings? I've just updated the Steps to reproduce, and added verification steps. I've also just tested on another new Magento project 2.4.3-1 as I wasn't able to get a develop instance, and was able to reproduce the issue.