Topology installation fails silently

[bartoszkubicki]

Preconditions (*)

1. Magento 2.3.3, PHP 7.3, Rabbit 3.7.8

Steps to reproduce (*)

1. Create topology having, for example queue, which causes exceptions from php-ampqlib, for example redeclare queue with different arguments values. (Possible if these PR are processed: Passing arguments for queues as expected #26966, Fix for queue numeric argument conversion #26967)
2. Magento topology installer catches exception, but only logs it, so we have a failure of installation, but in bin/magento setup:upgrade there is no info about that.
3. Caused here - vendor/magento/framework-amqp/TopologyInstaller.php:96

Expected result (*)

1. If whole setup:upgrade isn't stop, at least we have some message in the end, what went wrong

Actual result (*)

1. No info, so we pretend that setup went well.

[m2-assistant]

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

@bartoszkubicki 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.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[bartoszkubicki]

It should not be stale. It's need reviewing from @magento-engcom-team and decision if and how it can be fixed. My proposal is not catching an exception, so user is informed in console that something went wrong, not only in logs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!