Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1457879

Summary:	Host reinstallation commands don't appear as tasks in Tasks tab in webadmin
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	BLL.Infra	Assignee:	Miroslava Voglova <mvoglova>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.3	CC:	bugs, lsvaty, mperina, oourfali, tjelinek
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:32:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lucie Leistnerova 2017-06-01 12:41:43 UTC

Description of problem:
Reinstallation of the host should by a synchronous task so it should appear in tasks list, but is not there.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.1.3-0.1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. in engine try to add host with disabled vdsm repos, installation fails
2. enable vdsm repos on the host and reinstall the host in engine
3. look on the task list in the bottom of the page

Actual results: reinstallation is not in tasks list


Expected results: reinstallation is in tasks list


Additional info:
Adding host is in tasks and it contains installation, so the reinstallation seems similar to me.

Comment 1 Pavol Brilla 2017-11-21 13:09:38 UTC

Verified on 4.2.0-0.0.master.20171114111003.git7aa1b91

Reinstall is shown in tasks - verified

Comment 2 Sandro Bonazzola 2017-12-20 11:32:09 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.