Bug 1476845 - [DOCS] OCP 3.5 node out of space and installation documentation disk space requirements
Summary: [DOCS] OCP 3.5 node out of space and installation documentation disk space re...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks: 1724792
TreeView+ depends on / blocked
 
Reported: 2017-07-31 15:08 UTC by mdunn
Modified: 2019-06-28 16:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-01 21:29:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description mdunn 2017-07-31 15:08:39 UTC
Version-Release number of selected component (if applicable):
openshift v3.5.5.24


Document URL: 
https://access.redhat.com/documentation/en-us/openshift_container_platform/3.5/html-single/installation_and_configuration/

Section Number and Name: 
2.2.1.2 Minimum Hardware Requirements

Describe the issue: 
While running OCP 3.5, one of the nodes hit the out of disk space condition. This condition caused the removal of the glusterfs pod on that node, which was running CNS. I was asked to expand the filesystem in order to remedy the out of space condition. 
This node was provisioned with 50G of space for the /var/ file system. After reviewing the OCP 3.5 documentation, I see that the minimum requirement for a node is that the file system that contains /var/ needs to have 15G of space. Given that the /var/log/journal directory on this node grew to ~33G (more than double the aforementioned requirement) is that minimum requirement still valid?   

Though it is possible to expand the file system, it can definitely be a pain point.


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