Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magento unable to reindex bundle product not assigned to any sait (DisabledProductOptionPriceModifier.php on line 117). #35796

Closed
pret1 opened this issue Jul 22, 2022 · 9 comments
Labels
Area: Pricing Component: Indexer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@pret1
Copy link

pret1 commented Jul 22, 2022

Preconditions
Install Magento 2.4-develop with sample data.
 
Issue 
product price index (catalogproductprice) not working if bundle product not assigned to any website 
 
Steps To Reproduce
1)Go to admin ->catalog ->products -> create new bundle Or edit existing bundle product 
2)"Product in Websites" Tab  -> uncheck all checkboxes (website) and save the product 
3)Perform reindex 

 
Expected result
Reindex should be performed successfully 
 
Actual result
We get the below error while running the product price index
 

Warning: Undefined array key <bundel product id > in vendor/magento/module-bundle/Model/ResourceModel/Indexer/Price/DisabledProductOptionPriceModifier.php on line 117

 

 

@m2-assistant
Copy link

m2-assistant bot commented Jul 22, 2022

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


⚠️ 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
Copy link

m2-assistant bot commented Jul 22, 2022

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

    DetailsIf 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-Lima
Copy link
Contributor

✔️ Issue confirmed

Issue got reproduced in 2.4-develop branch.

Description: Magento unable to reindex catalog_product_price for bundle prioduct when we are not selecting any websites.

Pre-requisite:
Fresh magento 2.4-develop should be installed.

Steps to reproduce:

  1. Create bundle product
  2. In bundle product go to tab "Product in Websites" & uncheck the Websites.
  3. Click save & close.
  4. In CLI enter bin/magento indexer:reindex catalog_product_price

Expected result: Reindex success and catalog_product_price have a status ready.
Actual result: Reindex was not successfull and getting error as below screenshot:

reindex_issue

Additionally tested :
Also tested with other type of products like simple,configurable etc.
Hence, confirming the issue.

@engcom-Lima engcom-Lima added Component: Indexer Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Area: Pricing Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jul 25, 2022
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Jul 25, 2022
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6018 is successfully created for this GitHub issue.

@m2-assistant
Copy link

m2-assistant bot commented Jul 25, 2022

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@engcom-Hotel engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Jul 25, 2022
@m2-community-project m2-community-project bot added this to Ready for Development in High Priority Backlog Jul 25, 2022
@artskirk
Copy link

@magento I am working on this

@m2-community-project m2-community-project bot moved this from Ready for Development to Dev In Progress in High Priority Backlog Jul 26, 2022
artskirk pushed a commit to artskirk/magento2-1-fork that referenced this issue Jul 27, 2022
@m2-community-project m2-community-project bot moved this from Dev In Progress to Pull Request In Progress in High Priority Backlog Jul 27, 2022
artskirk pushed a commit to artskirk/magento2-1-fork that referenced this issue Jul 27, 2022
artskirk pushed a commit to artskirk/magento2-1-fork that referenced this issue Jul 27, 2022
artskirk pushed a commit to artskirk/magento2-1-fork that referenced this issue Jul 27, 2022
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Ready for Development in High Priority Backlog Oct 20, 2022
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in High Priority Backlog Oct 20, 2022
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in High Priority Backlog Oct 20, 2022
@chittima
Copy link
Contributor

Internal team is working on this issue

@hostep
Copy link
Contributor

hostep commented Nov 15, 2022

@chittima, @sdzhepa: can you please explain why this issue got closed?

@chittima
Copy link
Contributor

Issue is already fixed in the develop branch and not reproducible anymore. Here is the commit 0d90748

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Pricing Component: Indexer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
7 participants