Bug 1734732

Summary: [RFE] Add Log verbosity flag to Cockpit installer
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Gobinda Das <godas>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: low Docs Contact:
Priority: low    
Version: rhhiv-1.6CC: amukherj, bugs, godas, rhs-bugs, sabose, sasundar, seamurph
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHHI-V 1.6.z Async Update   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
More verbose (-vv) logging can now be enabled in the Web Console during deployment. Check the 'Enable debug logging' checkbox to use this feature.
Story Points: ---
Clone Of: 1713935 Environment:
Last Closed: 2019-10-03 12:24:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1713935    
Bug Blocks:    

Description Gobinda Das 2019-07-31 10:25:52 UTC
Description of problem:

Current Installer does not give any output when hitting a failure

User currently needs to modify /etc/ansible/ansible.conf and enable the following:
- logging + log location
- log verbosity

Would be nice to have a checkbox to add verbosity

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 SATHEESARAN 2019-08-28 05:57:50 UTC
Verified with cockpit-ovirt-dashboard-0.13.6

Gluster deployment wizard now has the checkbox - 'Enable debug logs'
Once this is checked, then the debug messages printed in the console

Comment 4 errata-xmlrpc 2019-10-03 12:24:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2963