magento2
magento2 copied to clipboard
Message queue topology is not considered in `setup:db:status` check
Preconditions and environment
- Magento 2.4.6-p3
- RabbitMQ configured
Steps to reproduce
- Run
setup:upgrade
to make sure db schema and data patches are up to date - Add a new binding inside a queue_topology.xml file
- Run
setup:db:status
Expected result
- Command will return exit code 2
- User is informed that
setup:upgrade
is needed
Actual result
- Command returns exit code 0
- Output is "All modules are up to date"
Additional information
Magento_Amqp module contains a recurring setup script that will upgrade the queue topology: \Magento\Amqp\Setup\Recurring. Updates to the topology configuration will only take effect when setup:upgrade
is run.
The command setup:db:status
should inform the user if a setup:upgrade
is needed or not. It is used by deployment scripts like the Magento 2 recipe of Deployer. If the command returns exit code 0, then setup:upgrade
is skipped during deployment and the message queue topology might be out of date.
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.
- [X] 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”.