Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1049359

Summary: Deleting paged queue does not remove underlying file
Product: Red Hat Enterprise MRG Reporter: Pavel Moravec <pmoravec>
Component: qpid-cppAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Irina Boverman <iboverma>
Severity: high Docs Contact:
Priority: medium    
Version: 3.0CC: freznice, iboverma, jross, lzhaldyb, vhubeika, zkraus
Target Milestone: 3.0Keywords: EasyFix, OtherQA, TestCaseProvided
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: qpid-cpp-0.22-35 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:09:41 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:
Attachments:
Description Flags
Trivial patch, committed to upstream already none

Description Pavel Moravec 2014-01-07 13:15:31 UTC
Description of problem:
When deleting a paged queue, the broker does not delete the underlying file it created in /var/lib/qpidd directory.


Version-Release number of selected component (if applicable):
MRG-M 3.0 EA (qpid-cpp 0.22-29)


How reproducible:
100%


Steps to Reproduce:
1. qpid-send -a "PagedQueue; {create:always, delete:always, node: { x-declare: {arguments: {'qpid.paging':'True' }}}}"
2. file /var/lib/qpidd/PagedQueue 


Actual results:
/var/lib/qpidd/PagedQueue: data


Expected results:
/var/lib/qpidd/PagedQueue: cannot open `/var/lib/qpidd/PagedQueue' (No such file or directory)


Additional info:

Comment 1 Pavel Moravec 2014-01-16 13:48:26 UTC
Created attachment 851079 [details]
Trivial patch, committed to upstream already

Committed to upstream as r1558790.

Comment 2 Pavel Moravec 2014-01-16 13:49:05 UTC
Upstream commit r1558790.

Comment 5 errata-xmlrpc 2014-09-24 15:09:41 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.

http://rhn.redhat.com/errata/RHEA-2014-1296.html