Bug 1740943

Summary:	Increasing Ansible verbosity level does not increase the verbosity of output
Product:	Red Hat Satellite	Reporter:	Danny Synk <dsynk>
Component:	Ansible - Configuration Management	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	egolov, lzap, nshaik, oprazak, swadeley
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_ansible-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:59:02 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 Danny Synk 2019-08-13 23:15:59 UTC

Description of problem:

Changing the value of Ansible's default verbosity setting in Satellite does not change the output of Ansible remote jobs.


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


How reproducible:
100% reproducible


Steps to Reproduce:

1. In the Satellite webUI, navigate to Administer >> Settings >> Ansible;

2. Change the value of the `Default verbosity level` setting to anything other than the default (which is `Disabled`);

3. Initiate an Ansible remote job run against a set of content hosts;

4. Navigate to the `Remote action` subtask for the job.


Actual results:

Output is the same regardless of the value of the `Default verbosity level` setting.


Expected results:

Output verbosity corresponds to the value of this setting.

Comment 3 Lukas Zapletal 2019-08-15 07:42:19 UTC

Hello,

I am not Ansible expert however before someone from the Satellite Ansible team picks up, I can comment that this setting should only add "ansible -vvvv" options. The more you set it more "-v" characters are appended.

Comment 4 Ondřej Pražák 2019-11-20 07:01:44 UTC

Created redmine issue https://projects.theforeman.org/issues/28312 from this bug

Comment 5 Nagoor Shaik 2019-12-02 16:17:00 UTC

This is fixed with https://projects.theforeman.org/issues/27236

Comment 6 Bryan Kearney 2019-12-02 17:06:54 UTC

Upstream bug assigned to aruzicka

Comment 7 Bryan Kearney 2019-12-02 17:06:56 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27236 has been resolved.

Comment 9 Lukas Pramuk 2020-09-21 22:53:09 UTC

VERIFIED.

@Satellite 6.8.0 Snap16
tfm-rubygem-foreman_ansible_core-3.0.3-1.el7sat.noarch

by the following manual reproducer:

1) Set ansible verbosity level to 'Level 4' (-vvvv) at Administer -> Settings -> tab Ansible - item 'Default verbosity level' 

2) Run ansible REX command against a host 

3) Inspect respective dynflow task:

___/ Run \______

 3: Actions::ProxyAction (success) [ 1010.67s / 0.01s ]

Queue: remote_execution

Started at: 2020-09-21 22:07:48 UTC

Ended at: 2020-09-21 22:24:38 UTC

Real time: 1010.67s

Execution time (excluding suspended state): 0.01s

Input: 
---
proxy_operation_name: ansible-runner
ansible_inventory:
...
verbosity_level: '4'
...

>>> verbosity level from setting is present in the proxy task

Comment 12 errata-xmlrpc 2020-10-27 12:59:02 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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366