Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1334743 - CFME log_rotate_freespace_check.sh uses wrong value to determine volume freespace causing logrotate to fail
CFME log_rotate_freespace_check.sh uses wrong value to determine volume frees...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.5.0
x86_64 Linux
high Severity high
: GA
: 5.5.4
Assigned To: Nick Carboni
Ramesh A
: ZStream
Depends On: 1294991
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-10 08:40 EDT by John Prause
Modified: 2017-08-29 22:03 EDT (History)
13 users (show)

See Also:
Fixed In Version: 5.5.4.1
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Mangement Engine, logrotate failed due to a reported insufficient space condition. CFME log_rotate_freespace_check.sh used incorrect value to determine volume freespace causing logrotate to fail. This patch changed the logrotate free space check script to read free space correctly which has now fixed the issue.
Story Points: ---
Clone Of: 1294991
Environment:
Last Closed: 2016-05-31 09:43:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1101 normal SHIPPED_LIVE CFME 5.5.4 bug fixes and enhancement update 2016-05-31 13:40:10 EDT

  None (edit)
Comment 6 errata-xmlrpc 2016-05-31 09:43:17 EDT
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-2016:1101

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