Description of problem:
The latest version (patchset 56) of README for oVirt.metrics-store-installation role says that bastion should be created by this command: 
./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --vault-password-file ./config.yml.d/secure_vars.yml

This command does not work for several reasons. 
1) If you want to refer secure_vars.yml, the path is wrong. When we are running this command, we are in /usr/share/ovirt-engine-metrics. The previous instructions tells us to go there. Let's try going to /usr/share/ovirt-engine-metrics and running this: 
# ls -l /config.yml.d/secure_vars.yml
ls: cannot access /config.yml.d/secure_vars.yml: No such file or directory

2) Even when you provide the correct path (/etc/ovirt-engine-metrics/config.yml.d/secure_vars.yml), it still does not work with --vault-password-file parameter. That is because --vault-password-file does not accept file with the ACTUAL sensitive data. It expects file with a password that UNLOCKS sensitive file (in our case secure_vars.yml).

3) We need to include our sensitive variables from secure_vars.yaml as extra vars. This is done with -e parameter. 

So if we want this command to execute successfully, we have to go one of two possible ways: 
1.1 Create a password file like this:
echo "<my_pass>" > password_file.txt
1.2 Then run:
./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --vault-password-file=password_file.txt
Or 
2. You can make Ansible to ask user for password interactively like this: 
./configure_ovirt_machines_for_metrics.sh --playbook=ovirt-metrics-store-installation.yml --ask-vault-pass

Version-Release number of selected component (if applicable):
ovirt-engine-metrics-1.2.1-0.0.master.20190225200554.el7.noarch (patchset 56)

How reproducible:
100 %

Steps to Reproduce:
1. Try running command that is supposed to deploy a bastino machine based on README for oVirt.metrics-store-installation role.