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:
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.
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
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.
*** Bug 1723458 has been marked as a duplicate of this bug. ***