Bug 731096

Summary:	Wrong assertion result using python client
Product:	Red Hat Enterprise MRG	Reporter:	Petr Matousek <pematous>
Component:	python-qpid	Assignee:	messaging-bugs <messaging-bugs>
Status:	NEW ---	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.0	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:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Matousek 2011-08-16 16:44:36 UTC

Description of problem:

Using assert in address string passed to python client do not give proper results

i.e.
# qpid-config add queue q
# drain "q;{assert:always, node:{durable:True}}"; echo $?
0
# drain "q;{assert:always, node:{x-declare: {exclusive:True}}}"; echo $?
0

The return code of the commands above shall be non-zero, commands shall output something like:
Queue not durable: q
Queue not exclusive: q

Other clients do not suffer from that.

Version-Release number of selected component (if applicable):
python-qpid-0.10-1.el6

How reproducible:
100%

Steps to Reproduce:

  
Actual results:
Wrong assertion results

Expected results:
Proper assertion results

Additional info:

Comment 2 Petr Matousek 2012-11-15 13:13:25 UTC

I would like to have also following case resolved by this bz:
# ./spout "ex;{ create:sender, node: { type:topic,x-declare:{type:topic}}}"
# ./spout "ex;{ assert: sender, node: { type:topic,x-declare:{type:fanout}}}"

Actual result:
both the messages are delivered to the exchange 'ex'

Expected result:
Exception like 'Exchange ex is of incorrect type, expected fanout but got topic' shall be thrown in step 2 instead of delivering the message