Bug 978867
| Summary: | qpid-config is allowing users to specify bogus policy settings | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Zdenek Kraus <zkraus> |
| Component: | qpid-tools | Assignee: | messaging-bugs <messaging-bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | Messaging QE <messaging-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.4 | CC: | 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: | 2025-02-10 03:28:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 978868 | ||
| Bug Blocks: | |||
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
Description of problem: qpid-config does not fails nor warn user that removed limit polices are not valid anymore, flow-to-disk and ring-strict. Version-Release number of selected component (if applicable): qpid-tools-0.22-2 How reproducible: 100% Steps to Reproduce: > qpid-config add queue x-reject --limit-policy=reject > qpid-config add queue x-ftd --limit-policy=flow-to-disk > qpid-config add queue x-ring --limit-policy=ring > qpid-config add queue x-ring-s --limit-policy=ring-strict Actual results: 2013-06-26 13:36:39 [Broker] notice Broker running 2013-06-26 13:38:07 [Broker] warning Unrecognised policy option: flow_to_disk 2013-06-26 13:38:52 [Broker] warning Unrecognised policy option: ring_strict Expected results: the client fails with error message and error code if the flow-to-disk or ring-strict are specified Additional info: