Bug 1748351

Summary: 'hours' is not a valid log rotation timeunit
Product: Red Hat Directory Server Reporter: Viktor Ashirov <vashirov>
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0CC: ebock, lkrispen, mhonek, pasik, spichugi, tbordaz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.4.1.7-1.module+el8dsrv+4200+233a821d Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-06 12:42:20 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 Viktor Ashirov 2019-09-03 12:19:17 UTC
Description of problem:
Audit, Audit fail, Access, Errors logs all have the same problem. One of the log rotation intervals in the dropdown menu is 'hours' which is not valid and is not accepted by the server. 


Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.6-2.module+el8dsrv+3912+aa2ce078.x86_64


How reproducible:
always

Steps to Reproduce:
1. See the links to comments below 
2.
3.

Actual results:


Expected results:


Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1623627#c9
https://bugzilla.redhat.com/show_bug.cgi?id=1623627#c10
https://bugzilla.redhat.com/show_bug.cgi?id=1623627#c12
https://bugzilla.redhat.com/show_bug.cgi?id=1623627#c14

Comment 2 Viktor Ashirov 2019-09-27 13:28:43 UTC
Builds tested:
389-ds-base-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.x86_64
cockpit-389-ds-1.4.1.9-1.module+el8dsrv+4243+ba0eb3c6.noarch

Rotation interval is 'hour' now, marking as VERIFIED.

Comment 4 errata-xmlrpc 2019-11-06 12:42:20 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/RHEA-2019:3731