Bug 1804097 - [test_day] Log file location for web console deployment is incorrect.
Summary: [test_day] Log file location for web console deployment is incorrect.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhiv-1.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHHI-V 1.7.z Async Update
Assignee: Disha Walvekar
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1804071
TreeView+ depends on / blocked
 
Reported: 2020-02-18 08:38 UTC by SATHEESARAN
Modified: 2020-02-26 08:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-26 08:05:59 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2020-02-18 08:38:48 UTC
Description of problem:
-----------------------
Chapter-12 describes the log file location of Web console deployment process.

Actual content is:
<snip>
The log file for the the Web Console based deployment process (documented in Chapter 7, Configure Red Hat Gluster Storage for Hosted Engine using the Web Console) is stored in the /var/log/ansible.log file by default. 
</snip>

The correct locations to log file:
- Gluster deployment & configuration from web console is located at /var/log/cockpit/ovirt-dashboard/gluster-deployment.log

Expected results:
-----------------
Update the correct location of web console deployment log from /var/log/ansible.log to  /var/log/cockpit/ovirt-dashboard/gluster-deployment.log

Comment 3 SATHEESARAN 2020-02-24 12:02:01 UTC
(In reply to Disha Walvekar from comment #2)
> Hi, 
> 
> I have corrected the log file location, please check the following link 
> 
> https://access.redhat.com/documentation/en-us/
> red_hat_hyperconverged_infrastructure_for_virtualization/1.7/html-single/
> deploying_red_hat_hyperconverged_infrastructure_for_virtualization/
> index?lb_target=preview#tshoot-log-files
> 
> Thank you!

Verified the content


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