Bug 1082026

Summary: 'unknown object' thrown where 'object exists' is expected
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: qpid-toolsAssignee: Gordon Sim <gsim>
Status: CLOSED ERRATA QA Contact: Michal Toth <mtoth>
Severity: low Docs Contact:
Priority: medium    
Version: DevelopmentCC: esammons, gsim, jross, mtoth
Target Milestone: 3.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-tools-0.30-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-14 13:47:46 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:

Description Petr Matousek 2014-03-28 13:53:19 UTC
Description of problem:

'unknown object type: domain' exception is reported instead of 'object already exists: new_domain' exception by qpid-config when creating already existing domain.

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-36
qpid-tools-0.22-9

How reproducible:
100%

Steps to Reproduce:
1. qpid-config  add domain new_domain --argument url=<broker_url> 
2. repeat step 1.
3. 'unknown object type: domain'

Actual results:
'unknown object type: domain' exception

Expected results:
'object already exists: new_domain' exception

Additional info:
# qpid-config  add domain new_domain --argument url=<broker_url>
# qpid-config  add domain new_domain --argument url=<broker_url>
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text': 'unknown object type: domain'}

Comment 1 Gordon Sim 2014-04-16 19:31:52 UTC
Fixed upstream: https://svn.apache.org/r1587999

Comment 3 Michal Toth 2014-10-21 08:23:26 UTC
Expected exception message is thrown. 
Verified on 
qpid-tools-0.30-1
qpid-cpp-*-0-30-2

Comment 5 errata-xmlrpc 2015-04-14 13:47:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0805.html