Bug 1713935

Summary:	[RFE] Add Log verbosity flag to Cockpit installer
Product:	[oVirt] cockpit-ovirt	Reporter:	Sean Murphy <seamurph>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	low	Docs Contact:
Priority:	low
Version:	0.12.4	CC:	amukherj, bugs, godas, rhs-bugs, sabose, sasundar
Target Milestone:	ovirt-4.3.6	Keywords:	ZStream
Target Release:	0.13.6	Flags:	sbonazzo: ovirt-4.3?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.13.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1734732 (view as bug list)		Environment:
Last Closed:	2019-09-26 19:42:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1734732

Description Sean Murphy 2019-05-25 20:56:46 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 Sachidananda Urs 2019-05-27 03:37:02 UTC

We can add the log location to ansible.cfg, verbosity is obtained by calling the playbook with -vv option which can be taken care by cockpit.

Comment 5 SATHEESARAN 2019-08-28 05:58:17 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 6 Sandro Bonazzola 2019-09-26 19:42:54 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

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