Bug 1090642
Summary: | Running ccs -f testfile creates a temp file for the schema but never removes it | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Feist <cfeist> |
Component: | ricci | Assignee: | Chris Feist <cfeist> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.6 | CC: | cluster-maint, jruemker, nobody, rsteiger |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ccs-0.16.2-71.el6 | Doc Type: | Bug Fix |
Doc Text: |
Cause: ccs did not properly dispose of temporary files created when editing the cluster.conf file locally with the '-f' option.
Consequence: A large number of temporary files could be left in the temporary directory
Fix: ccs properly removes temporary files it creates.
Result: The filesystem temporary directory will no longer fill up with a large number of files if multiple ccs commands using the '-f' option are executed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-14 07:30:06 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
Chris Feist
2014-04-23 20:17:22 UTC
Before fix, leftover tmp files in /tmp/ [root@bid-06 ~]# rpm -q ccs ccs-0.16.2-69.el6_5.1.x86_64 [root@bid-06 ~]# ls /tmp/ | grep tmp [root@bid-06 ~]# ccs -f testfile --createcluster hi [root@bid-06 ~]# ls /tmp/ | grep tmp tmp9Uy45y After fix: [root@bid-06 ~]# rpm -q ccs ccs-0.16.2-71.el6.x86_64 [root@bid-06 ~]# ls /tmp/ | grep tmp [root@bid-06 ~]# ccs -f testfile --createcluster hi [root@bid-06 ~]# ls /tmp/ | grep tmp [root@bid-06 ~]# 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/RHBA-2014-1539.html |