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

Purchase of product with all/last pcs leave product available in catalog (until manual cache flush) #35105

Closed
5 tasks
nkajic opened this issue Feb 15, 2022 · 10 comments
Labels
Area: Catalog Issue: needs update Additional information is require, waiting for response Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@nkajic
Copy link
Member

nkajic commented Feb 15, 2022

Preconditions (*)

  1. development branch

Steps to reproduce (*)

  1. Add product in cart with max quantity available (usually 100 pcs in sample data)
  2. Finish checkout
  3. Go to category where that product was available
  4. Add to cart

Expected result (*)

  1. Product IS NOT shown in category
  2. Product does not have Add to cart button available

Actual result (*)

  1. Product is shown in category
  2. Product Add to cart button is available
  3. Clicking Add to cart leads to Product page showing error "The requested qty is not available"

Recording from testing
https://youtu.be/ZrknzyYy2EI


Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant
Copy link

m2-assistant bot commented Feb 15, 2022

Hi @nkajic. 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 Feb 16, 2022

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

    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-Hotel
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @engcom-Hotel. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@engcom-Hotel
Copy link
Contributor

Hello @nkajic,

We have tried to reproduce the issue in Magento 2.4-develop branch, the issue is reproducible for us. Please have a look into the below screenshots for reference:

  • In the admin panel, the catalog list page shows 0 default stock:
    image

  • Product Shown in the category:
    image

  • Error on Add to cart:
    image

  • After clearing the cache, the product is not visible in the category page:
    image

Note: I have waited for some time like 5 mins if the cache will clear automatically. But that does not happen.

Hence confirming the issue.

Thanks

@engcom-Hotel engcom-Hotel added Area: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch labels Feb 16, 2022
@github-jira-sync-bot
Copy link

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

@m2-assistant
Copy link

m2-assistant bot commented Feb 16, 2022

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

@sdzhepa
Copy link
Contributor

sdzhepa commented Feb 17, 2022

@engcom-Hotel @nkajic

This issue could occur on instances where consumers are not runing(configured)
https://devdocs.magento.com/guides/v2.4/config-guide/cli/config-cli-subcommands-queue.html

Could you please confirm is it issue happened with enabled/configured consumers on an instance with MSI

@sdzhepa sdzhepa added the Issue: needs update Additional information is require, waiting for response label Feb 17, 2022
@m2-community-project m2-community-project bot removed the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Feb 17, 2022
@nkajic
Copy link
Member Author

nkajic commented Feb 17, 2022

Hi all,

I have managed to get it working by properly configuring consumers.

Are't consumers configured to run on test instances by magento-deployment-service? Maybe I have tested it before consumers were ready to accept jobs?

I will close this issue. Thanks all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Catalog Issue: needs update Additional information is require, waiting for response Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

No branches or pull requests

4 participants