Bug 1715519

Summary: No option for verbose mode when installing metrics store
Product: [oVirt] ovirt-engine-metrics Reporter: Ivana Saranova <isaranov>
Component: GenericAssignee: Yedidyah Bar David <didi>
Status: CLOSED CURRENTRELEASE QA Contact: Ivana Saranova <isaranov>
Severity: medium Docs Contact:
Priority: high    
Version: 1.3.1CC: bugs, didi, dvaanunu, lleistne, sradco
Target Milestone: ovirt-4.3.5Keywords: Regression, ZStream
Target Release: 1.3.3Flags: sradco: ovirt-4.3?
sbonazzo: planning_ack?
sbonazzo: devel_ack+
lleistne: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-metrics-1.3.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-30 14:08:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1723786    

Description Ivana Saranova 2019-05-30 14:28:15 UTC
Description of problem:
When installing metrics, you can't run the installation script with -v option for verbose mode to see more detailed output. The only option how to achieve the verbose mode is to manually add the -v option to the script.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.4.1-0.1.el7.noarch
ovirt-engine-metrics-1.3.1-1.el7ev.noarch
ansible-2.8.0-1.el7ae.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run the installation script with -v (or -vv, -vvv,..)

` ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do" ./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -v`

2. Check that the output is in verbose mode

Actual results:

[root@engine ovirt-engine-metrics]# ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do" ./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -v
Usage: ansible-playbook [options] playbook.yml [playbook2 ...]

ansible-playbook: error: no such option: --ask-vault-pass-v


[root@engine ovirt-engine-metrics]# ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do" ./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -vvv
Usage: ansible-playbook [options] playbook.yml [playbook2 ...]

ansible-playbook: error: no such option: --ask-vault-pass-vvv


Expected results:
Output is in verbose mode.

Additional info:

Comment 1 Yedidyah Bar David 2019-06-24 07:07:51 UTC
QE:(In reply to Ivana Saranova from comment #0)
> Description of problem:
> When installing metrics, you can't run the installation script with -v
> option for verbose mode to see more detailed output. The only option how to
> achieve the verbose mode is to manually add the -v option to the script.
> 
> Version-Release number of selected component (if applicable):
> ovirt-engine-4.3.4.1-0.1.el7.noarch
> ovirt-engine-metrics-1.3.1-1.el7ev.noarch
> ansible-2.8.0-1.el7ae.noarch
> 
> How reproducible:
> Always
> 
> Steps to Reproduce:
> 1. Run the installation script with -v (or -vv, -vvv,..)
> 
> ` ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do"
> ./configure_ovirt_machines_for_metrics.sh
> --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -v`
> 
> 2. Check that the output is in verbose mode
> 
> Actual results:
> 
> [root@engine ovirt-engine-metrics]#
> ANSIBLE_JINJA2_EXTENSIONS="jinja2.ext.do"
> ./configure_ovirt_machines_for_metrics.sh
> --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass -v
> Usage: ansible-playbook [options] playbook.yml [playbook2 ...]
> 
> ansible-playbook: error: no such option: --ask-vault-pass-v

The bug was unrelated to verbose mode specifically, but that all arguments that were passed on to ansible (and not processed by the script itself, see bug 1471833) were concatenated. In above example, '--ask-vault-pass' and '-v' became '--ask-vault-pass-v'.

This means that passing only '-v' did work.

Comment 2 Ivana Saranova 2019-07-12 09:16:46 UTC
Steps:
1) Run installation script with more arguments (for example with -v)
2) Check that the arguments aren't concatenated and playbook uses the additional arguments correctly

Result:
Arguments are not concatenated. Playbook uses the additional arguments correctly.

Verified in:
ovirt-engine-4.3.5.3-0.1.el7.noarch
ovirt-engine-metrics-1.3.3.1-1.el7ev.noarch

Comment 3 Sandro Bonazzola 2019-07-30 14:08:45 UTC
This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 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.

Comment 4 Shirly Radco 2019-08-22 10:47:42 UTC
*** Bug 1723458 has been marked as a duplicate of this bug. ***