| Summary: | msgGroups: Invalid configuration request while creating the message group queue leads to common queue creation, no error is passed to management | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Petr Matousek <pematous> |
| Component: | qpid-tools | Assignee: | Ken Giusti <kgiusti> |
| Status: | NEW --- | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | Development | CC: | iboverma, jross |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 734115 | ||
| Bug Blocks: | |||
some more info:
This issue is not only related to grouping policy. It is more general. Invalid configuration request while creating the message group queue leads to "vanilla" queue creation, no error is passed to the management.
There are some more examples:
Specifying empty string for group header either with addressing method or with qpid-config leads to similar result. The results a bit differ per method used (see below), but both of these queues are NOT configured for message groups mode.
# ./spout "q;{create:sender,delete:never,node:{x-declare:{arguments:{'qpid.group_header_key':'','qpid.shared_msg_group':True}}}}"
Queue Name Attributes
===================================
q2 --group-header= --shared-groups
# qpid-config add queue q5 --group-header='' --shared-groups
Queue Name Attributes
===================================
q2 --shared-groups
If you provide not a string (ie. number, map..) to qpid.group_header_key in the address,
ie. arguments:{'qpid.group_header_key':5,'qpid.shared_msg_group':True}
there is no error passed to the management and "vanilla" queue is
created instead as well. etc.
changing the "Summary" to be more corresponding to the reported issue. |
Description of problem: qpid-config add queue q --group-header="GROUP_KEY" (user forget to specify "--shared-group" option) # qpid-config queues | grep "^q " q --group-header=GROUP_KEY If the grouping policy is not specified the queue is created and acts as a normal queue (is not configured for the group mode, no error is displayed) The same result is by using the addressing method ('qpid.shared_msg_group':True omited): # ./spout "q;{create:always,assert:always,delete:always,node:{x-declare:{arguments:{'qpid.group_header_key':'GROOUP-KEY'}}}}" The grouping policy shall be mandatory option when "group-header" option specified. (at least with the qpid-config method) Version-Release number of selected component (if applicable): python-qpid-0.14-1.el5 python-qpid-qmf-0.14-2.el5 qpid-cpp-client-0.14-3.el5 qpid-cpp-client-devel-0.14-3.el5 qpid-cpp-client-devel-docs-0.14-3.el5 qpid-cpp-client-ssl-0.14-3.el5 qpid-cpp-server-0.14-3.el5 qpid-cpp-server-cluster-0.14-3.el5 qpid-cpp-server-devel-0.14-3.el5 qpid-cpp-server-ssl-0.14-3.el5 qpid-cpp-server-store-0.14-3.el5 qpid-cpp-server-xml-0.14-3.el5 qpid-java-client-0.14-1.el5 qpid-java-common-0.14-1.el5 qpid-java-example-0.14-1.el5 qpid-qmf-0.14-2.el5 qpid-qmf-devel-0.14-2.el5 qpid-tests-0.14-1.el5 qpid-tools-0.14-1.el5 How reproducible: 100% Steps to Reproduce: see problem description above Actual results: If the grouping policy is not specified when creating the message group queue, the queue is NOT configured for the group mode even if the group header was specified Expected results: The grouping policy shall be mandatory option when "group-header" option specified. (at least with the qpid-config method)