Bug 1463819 - Orphaned qpid journal files when unregistering a content host
Summary: Orphaned qpid journal files when unregistering a content host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Qpid
Version: 6.2.8
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Mike Cressman
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-21 19:42 UTC by Satellite Program
Modified: 2019-04-01 20:27 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1443470
Environment:
Last Closed: 2018-02-21 12:57:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-7788 0 None None None 2017-06-21 19:42:49 UTC
Red Hat Product Errata RHBA-2018:0338 0 normal SHIPPED_LIVE Red Hat Satellite 6.3 Tools 2018-02-21 19:30:02 UTC

Comment 2 Radovan Drazny 2017-09-20 13:25:02 UTC
Verified on Satellite 6.3, qpid-cpp-server-1.36.0-9.el7 using the reproducer from the original report. 

On a Satellite client the following loop was running:

while true; 
do 
  subscription-manager register --org="Default_Organization" --username=admin --password=nimda 
  sleep 5
  systemctl restart goferd
  sleep 5
  subscription-manager unregister
done

Monitoring the /var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use dir on the Sat 6.3 server using following commands:

ls in_use | wc -l
du -ks in_use

The directory wasn't completely stable, but the number of files and present and consumed disk space always went down after a short (and not too high) spike, so qpid server was cleaning up old files and not leaving orphans. 

VERIFIED

Comment 5 errata-xmlrpc 2018-02-21 12:57:54 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://access.redhat.com/errata/RHBA-2018:0338


Note You need to log in before you can comment on or make changes to this bug.