Bug 1690833 - host is not upgraded when already in maintenance mode
Summary: host is not upgraded when already in maintenance mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.3.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.3
: ---
Assignee: Ravi Nori
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-20 10:28 UTC by Lucie Leistnerova
Modified: 2019-04-16 13:58 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.3.3.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-16 13:58:08 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.3+
lleistne: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98712 0 master MERGED engine: Host is not upgraded when already in maintenance mode 2019-03-21 13:28:23 UTC
oVirt gerrit 98759 0 ovirt-engine-4.3 MERGED engine: Host is not upgraded when already in maintenance mode 2019-03-24 10:52:10 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.