Description of problem:
Hosted-engine installation with ansible should support 'tags' and 'skip-tags' properties.
hosted-engine's ansible playbooks should have the possibility to use tags in them.
The reason to add 'tags' support is that ovirt-ansible-roles projects are using tags almost for each playbook. Thus, if we would like to use some of these roles we need to have the possibility to use 'tags' or 'skip-tags'.
Moving out to 4.2.8 not being identified as blocker for 4.2.8
Moving out to 4.2.8 not being identified as blocker for 4.2.7
Please provide more details about reproduction steps.
There are no special reproduction steps - just install hosted-engine with:
1. hosted-engine --deploy via CLI
2. Via cockpit
3. Directly with the ansible role
Regarding 3, we will change the usage as it appear here : https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/#usage
and add a tag to be used.
(In reply to Ido Rosenzwig from comment #5)
> There are no special reproduction steps - just install hosted-engine with:
> 1. hosted-engine --deploy via CLI
> 2. Via cockpit
> 3. Directly with the ansible role
> Regarding 3, we will change the usage as it appear here :
> and add a tag to be used.
Regarding step 3, what do you mean with ansible role?
Ansible role is now the default deployment under the hood, so nothing is required to deploy from interactive user deployment perspective, other than simply make regular deployment. Am I right?
You are right that the ansible role is used under the hood in the hosted-engine deployment if you run 'hosted-engine --deploy'
But you can also deploy hosted-engine just with the ansible role.
Please refer to the README.md here  which explains it all with some examples
Regular CLI deployment of HE over iSCSI works well with these components:
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Moving to verified.
Please reopen if you still see any issues.
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.
Since the problem described in this bug report should be
resolved in oVirt 4.3.1 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.