Bug 1615137

Summary: [Docs][Data Warehouse Guide] Need detailed steps to enter postgresql command line
Product: Red Hat Enterprise Virtualization Manager Reporter: Abhishekh Patil <abpatil>
Component: DocumentationAssignee: Tahlia Richardson <trichard>
Status: CLOSED CURRENTRELEASE QA Contact: Avital Pinnick <apinnick>
Severity: unspecified Docs Contact:
Priority: high    
Version: 4.2.3CC: apinnick, lbopf, lsurette, pkovar, srevivo, tburke, trichard
Target Milestone: ovirt-4.2.6Keywords: FutureFeature, Triaged
Target Release: ---Flags: lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: docs-accepted
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-24 01:17:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Abhishekh Patil 2018-08-12 15:07:54 UTC
1. Proposed title of this feature request:
  
Need detailed steps to enter postgresql command line in RHV-4.2 data warehouse guide. 


2. Why does the customer need this?

  
    From RHV-4.2, rh-postgresql95-postgresql package is used which is a 9.5 version of Postgresql. This package is a part of Red Hat Software Collections (RHSCL). We won't be able to run the commands installed from RHSCL directly. We have to enable the scl environment first. In the following data warehouse guide (for section '2.6. Allowing Read-Only Access to the History Database') the step for enabling the scl environment before running psql commands for RHV-4.2 is missing:

    https://access.redhat.com/documentation/enus/red_hat_virtualization/4.2/html-single/data_warehouse_guide/#Allowing_Read_Only_Access_to_the_History_Database


We have to add following step before running psql commands:

#.scl_source enable rh-postgresql95

Comment 3 Avital Pinnick 2018-08-22 09:20:59 UTC
*** Bug 1611038 has been marked as a duplicate of this bug. ***