Bug 1690833

Summary:	host is not upgraded when already in maintenance mode
Product:	[oVirt] ovirt-engine	Reporter:	Lucie Leistnerova <lleistne>
Component:	General	Assignee:	Ravi Nori <rnori>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Kubica <pkubica>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.2.1	CC:	bugs, mperina, rnori
Target Milestone:	ovirt-4.3.3	Flags:	pm-rhel: ovirt-4.3+ lleistne: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.3.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-16 13:58:08 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 2019-03-20 10:28:59 UTC

Description of problem:
Clicking on Upgrade by host that is already in maintenance mode starts the upgrade but nothing more happens.

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

How reproducible: always


Steps to Reproduce:
1. have host with newer rpms available
2. put the host in maintenance
3. click on Installation -> Upgrade

Actual results: in events:
Host vhost01 upgrade was started (User: admin@internal-authz).
and nothing more. No error in any log.


Expected results: upgrade starts

Additional info:
Clicking on Upgrade on active host works as expected.

Comment 1 Petr Kubica 2019-04-03 10:01:31 UTC

Verified in ovirt-engine-4.3.3.1-0.1.el7.noarch

Comment 2 Sandro Bonazzola 2019-04-16 13:58:08 UTC

This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 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.