Bug 1598141

Summary:	[RFE] HE Node Zero should support 'tags' and 'skip-tags' properties
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Ido Rosenzwig <irosenzw>
Component:	General	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.2.23	CC:	bugs, emarcus, irosenzw
Target Milestone:	ovirt-4.3.1	Keywords:	FutureFeature, Performance, Triaged
Target Release:	---	Flags:	rule-engine: ovirt-4.3? mavital: testing_plan_complete? rule-engine: planning_ack? sbonazzo: devel_ack+ rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.12.2	Doc Type:	Enhancement
Doc Text:	In this release, self-hosted engine installation supports Ansible playbooks that use tags.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 10:20:15 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:

Description Ido Rosenzwig 2018-07-04 12:40:52 UTC

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.

Comment 1 Ido Rosenzwig 2018-07-05 06:51:36 UTC

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'.

Comment 2 Sandro Bonazzola 2018-09-21 08:05:52 UTC

Moving out to 4.2.8 not being identified as blocker for 4.2.8

Comment 3 Sandro Bonazzola 2018-09-21 08:06:08 UTC

Moving out to 4.2.8 not being identified as blocker for 4.2.7

Comment 4 Nikolai Sednev 2019-01-31 05:38:41 UTC

Please provide more details about reproduction steps.

Comment 5 Ido Rosenzwig 2019-01-31 07:01:48 UTC

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.

Comment 6 Nikolai Sednev 2019-01-31 07:09:47 UTC

(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 :
> https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/#usage
> 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?

Comment 7 Ido Rosenzwig 2019-01-31 07:20:59 UTC

Almost.
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 [1] which explains it all with some examples

[1] https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/README.md

Comment 8 Nikolai Sednev 2019-02-26 13:31:18 UTC

Regular CLI deployment of HE over iSCSI works well with these components:
rhvm-appliance-4.3-20190220.2.el7.x86_64
ansible-2.7.8-1.el7ae.noarch
ovirt-ansible-engine-setup-1.1.8-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.5-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
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.

Comment 9 Sandro Bonazzola 2019-03-01 10:20:15 UTC

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.