setup:db:status cli doesn't track queue consumer changes

[Vigneshmuthusamy]

Preconditions and environment

• Magento version - Old and latest versions till 2.4.6
• Occurs in both commerce and open source editions
• We need to have message queue configured to test it

Steps to reproduce

• Setup message queues and add new topics/queues via any existing custom module
• run bin/magento setup:db:status command to check for db schema changes
• It'll output All modules are up to date. even though we have new DB changes to the queue table

Expected result

Whenever we run bin/magento setup:db:status command to check for DB schema changes, it'll output if we should run setup:upgrade for the DB schema changes to reflect.

Since we have new queue created and DB changes waiting to be updated which should show the correct status on status cli.

Actual result

It's showing All modules are up to date. even though we have new DB changes to the queue table

Additional information

No response

Release note

No response

Triage and priority

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

Hi @Vigneshmuthusamy. Thank you for your report.
To speed up processing of this issue, 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.

[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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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 @Vigneshmuthusamy ,
Thank you for reporting and collaboration. Verified the behavior on Magento 2.4-develop instance and is reproducible. But however this seems to be expected behavior but not a bug. On setting up the message queues as per docs / Configure the consumers behavior or creating the deployment configuration using bin/magento setup:config:set command as per docs does not require setup:upgrade operation from CLI to update the modules as the values being set are updated without the need of setup:upgrade. Kindly refer the docs and provide your inputs on this.
Thank you.

[Vigneshmuthusamy]

ok. But even the config values tracked in config.php that was dumped using app:conf:dump also didn't output correct status on any updates. Only the changes in module node shows we need to run the setup:upgrade. Is that also expected behavior?

[engcom-November]

Thank you for the response @Vigneshmuthusamy . As per Magento devdocs, after we configure settings in the Magento Admin, we export those settings to configuration files using command: app:config:dump and this does not require setup:upgrade operation to update the configuration files or on the UI and is an expected behavior. Kindly refer the docs and let us know if you face any issues.
Thank you.

[engcom-Bravo]

Hi @Vigneshmuthusamy,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

[hostep]

This was incorrectly closed, but is now confirmed in a new issue: #38225