Magento2: Bulk product attribute not updated in magento 2.3.2

[santosh-ks153]

Preconditions (*)

1. PHP 7.2.27
2. MySql 5.6.40

Steps to reproduce (*)

1. Go to Admin -> Catalog -> Product
2. Select multiple products from product grid
3. Choose Update Attributes from Action drop-down
4. Change any attribute and Save

Expected result (*)

1. Product attribute should be updated.

Actual result (*)

1. Product attribute not updated
   

[magento-deployment-service[bot]]

Thanks for opening this issue!

[m2-assistant[bot]]

Hi @santosh-ks153. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@santosh-ks153 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-deployment-service[bot]]

Thanks for opening this issue!

[m2-assistant[bot]]

Hi @sudheers-kensium. 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:

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

[sudheers-kensium]

@santosh-ks153 Can you please update more details.

[santosh-ks153]

when I m trying to update the product attribute using Magento backend. got the below message always.

[santosh-ks153]

Look like it will never updates the product attribute.

[santosh-ks153]

Any solution for that @sudheers-kensium

[sudheers-kensium]

@santosh-ks153 You need to enable the magento cron

[santosh-ks153]

I did still showing the same issue

[magento-engcom-team]

:white_check_mark: Confirmed by @sudheers-kensium
Thank you for verifying the issue. Based on the provided information internal tickets MC-31078 were created

Issue Available: @sudheers-kensium, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[magento-deployment-service[bot]]

Thanks for opening this issue!

[darshankhatri16]

Hi @santosh-ks153
You need to enable start queue consumer "product_action_attribute.update". You can list out all the consumers via below command:
php bin/magento queue:consumers:list

Please find below screenshot

You can start consumer by below command:
php bin/magento queue:consumers:start product_action_attribute.update

Let me know if you need any further details.

[santosh-ks153]

after doing the above I got the below response.

[darshankhatri16]

Could you please try below command with area-code
php bin/magento queue:consumers:start product_action_attribute.update --area-code='adminhtml'

[santosh-ks153]

Getting the same issue.

[darshankhatri16]

@santosh-ks153
I did some research on this issue and found that you have installed some custom module and in that custom module, you will find a code where area code has been set. Could you please verify in your custom module?
This is usually due to some other bit of code setting the areaCode before the core is trying to set it. Usually, because it is trying to be set in __construct() somewhere. With how dependency injection works, all objects are loaded and their constructors are run, even if you're not using that object. I would check that the areaCode is not being set in a __construct()

[SewHappy58]

I'm having the same issue on Magento 2.3.5-p1. It's a clean install but I imported products. I tried php bin/magento queue:consumers:list but nothing happened

[GalichMolodothon]

Could somebody clarify
I run bin/magento queue:consumers:start product_action_attribute.update and it started working.
We should run and configure it like cron? I could found information about it and that is so important.

[hostep]

@GalichMolodothon: the default Magento cron has a job called consumers_runner which should already spawn these consumer processes, so normally you only need to call bin/magento cron:run.

But that can change depending on your configuration of those consumers. See the documentation for this, the default configuration shouldn't block consumers, but maybe somehow the configuration got changed in your particular case?

[sdzhepa]

Hello @santosh-ks153
cc: @GalichMolodothon @SewHappy58 @hostep

Based on the issue description and discussion in comments
It seems not a bug but a configuration issue.
also in comments, there are recommendations, guides and links to the official documentation.

Please confirm that we close this Issue or update information in the issue description

[GalichMolodothon]

@sdzhepa hello!
Yes, it was a misunderstanding for setting the correct format in the cloud configuration for consumers and setting an array of consumers.