Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Skip rabbit_mqtt_qos0_queue_kill_node in mixed version mode (#10210)
* Skip rabbit_mqtt_qos0_queue_kill_node in mixed version mode Follow up of #10205 Branch v3.12.x is currently red because test ``` bazel test //deps/rabbitmq_mqtt:shared_SUITE-mixed -t- --test_sharding_strategy=disabled --test_env FOCUS="-group [mqtt,cluster_size_3] -case rabbit_mqtt_qos0_queue_kill_node" ``` fails because the old node will error out with: ``` [info] <0.1962.0> accepting MQTT connection <0.1962.0> (127.0.0.1:61899 -> 127.0.0.1:21059, client id: subscriber) [debug] <0.1962.0> Received a SUBSCRIBE for topic(s) [{mqtt_topic, [debug] <0.1962.0> "rabbit_mqtt_qos0_queue_kill_node",0}] [error] <0.1977.0> Channel error on connection <0.1965.0> (127.0.0.1:61899 -> 127.0.0.1:21059, vhost: '/', user: 'guest'), channel 1: [error] <0.1977.0> operation queue.declare caused a channel exception resource_locked: cannot obtain exclusive access to locked queue 'mqtt-subscription-subscriberqos0' in vhost '/'. It could be originally declared on another connection or the exclusive property value does not match that of the original declaration. ``` Classic mirrored queue could be used instead as descibed in https://groups.google.com/g/rabbitmq-users/c/pxgy0QiwilM/m/LkJQ-3DyBgAJ PR #10205 specifically allows for clients to re-subscribe to a live node for queue type rabbit_mqtt_qos0_queue. So, it's okay to skip the test when run with feature flag rabbit_mqtt_qos0_queue being disabled causing a classic queue to be created. * Ensure test is skipped
- Loading branch information