Bug 1630878

Summary: The disk speed range needs to be updated as per limit mentioned in the installation guide
Product: Red Hat Satellite Reporter: Ashish Humbe <ahumbe>
Component: Satellite MaintainAssignee: Kavita <kgaikwad>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: apatel, inecas, kgaikwad, mbacovsk
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-20 08:02:03 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 Ashish Humbe 2018-09-19 13:28:19 UTC
Description of problem:

On a physical system installed with Satellite 6.3 when we try to upgrade to 6.4 Beta, the foreman-maintain upgrade check failed due to disk speed check. 


=====================
Check for recommended disk speed of pulp, mongodb, pgsql dir.: 
| Finished                                                                      

Disk speed : 79 MB/sec                                                [FAIL]
Slow disk detected /var/lib/pulp mounted on /dev/mapper/rhel_dell--per320--3-root.
             Actual disk speed: 79 MB/sec
             Expected disk speed: 80 MB/sec.

=====================

The Storage Guidelines section in the installation guide[1] says the disk speed should be "60 - 80 Megabytes per second" 


Current disk speed check of 80 MB/s needs to be changed to 60 MB/s. 

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4-beta/html-single/installation_guide/#hardware_storage_prerequisites

Comment 1 Satellite Program 2018-09-19 14:07:29 UTC
Upstream bug assigned to kgaikwad

Comment 2 Satellite Program 2018-09-19 14:07:32 UTC
Upstream bug assigned to kgaikwad

Comment 3 Kavita 2018-09-20 08:02:03 UTC

*** This bug has been marked as a duplicate of bug 1574260 ***