Bug 1731358 - Supported time units for Logging Ansible Variables
Summary: Supported time units for Logging Ansible Variables
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Anping Li
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-19 08:48 UTC by Robert Sandu
Modified: 2019-09-18 06:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Robert Sandu 2019-07-19 08:48:44 UTC
Document URL: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html-single/configuring_clusters/index#aggregate-logging-ansible-variables

Section Number and Name: "36.3. Specifying Logging Ansible Variables"

Describe the issue: Section 36.3, in the "Configuring clusters" document, is missing a section for supported time units.

An example is `openshift_logging_es_recover_after_time`, which admits either seconds (s) or minutes (m) as time unit value.

Suggestions for improvement: add a note of supported time units in the `Logging Ansible Variables` section, like the one seen in [1].

`Supported time units are microseconds (us), milliseconds (ms), seconds (s), minutes (m), hours (h), or days (d).`

---

[1] https://docs.openshift.com/container-platform/4.1/networking/routes/route-configuration.html#nw-configuring-route-timeouts_route-configuration


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