Bug 1490386

Summary:	Host upgrade fails if run immediately after check for upgrade
Product:	[oVirt] ovirt-engine	Reporter:	Petr Matyáš <pmatyas>
Component:	BLL.Infra	Assignee:	Ondra Machacek <omachace>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.6	CC:	bugs, oourfali
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
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:44:42 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:
Bug Depends On:	1380498
Bug Blocks:

Description Petr Matyáš 2017-09-11 12:54:25 UTC

Description of problem:
If I run 'Check for upgrade' and immediately after that I click on 'Upgrade' the host gets to 'Install failed' state, just because there was a lock, from the 'Check for upgrade', on yum. The 'Upgrade' should wait for 'Check for upgrade' to finish and start after that.

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

How reproducible:
always

Steps to Reproduce:
1. run check for upgrade and immediately run upgrade
2.
3.

Actual results:
host is in install failed state

Expected results:
host should be up after upgrade finishes

Additional info:

Comment 1 Martin Perina 2017-09-15 12:13:32 UTC

The whole flow will be completely reimplemented using Ansible, so let's retest when BZ1380498 is finished

Comment 2 Ondra Machacek 2017-10-25 08:05:14 UTC

Shouldn't happen in 4.2 as we changed the proccess in #1380498, please re-test in 4.2.

Comment 3 Petr Matyáš 2017-10-25 08:47:34 UTC

Every other run of check for update, when one is already running, results in a warning that another check is already running, hence the check is not running multiple times and there is no failed to install state of host or errors present.

Verified on ovirt-engine-4.2.0-0.0.master.20171023193344.gitc3b23f6.el7.centos.noarch

Comment 4 Sandro Bonazzola 2017-12-20 11:44:42 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.