Bug 1631215

Summary: Upgrade of hosts causes no warning/error/change of status when running VMs are pinned to hosts
Product: [oVirt] ovirt-engine Reporter: Jiri Belka <jbelka>
Component: Frontend.WebAdminAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.6.2CC: akrejcir, bugs, mperina, pbrilla, rnori
Target Milestone: ovirt-4.2.8Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.8.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-22 10:23:41 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:
Attachments:
Description Flags
engine log with ERROR message none

Description Jiri Belka 2018-09-20 08:51:55 UTC
Description of problem:

In an OCP on RHV env, there are running VMs which are pinned to hosts. While a host shows there is available update, executing Upgrade action on such running host causes nothing - I can see only 'Host <host> upgrade was started.'

Version-Release number of selected component (if applicable):
4.2.6.4-0.1.el7ev

How reproducible:
100%

Steps to Reproduce:
1. have a running host with all runnings pinned to host
2. have available updates for a host, visible in Admin Portal
3. run Upgrade action via Upgrade button

Actual results:
there's only event with 'Host <host> upgrade was started.' but nothing more.

Expected results:
not sure but at least - a warning

Additional info:

Comment 1 Martin Perina 2018-09-20 12:32:16 UTC
Could you please attach logs?

Comment 2 Pavol Brilla 2018-09-20 12:47:03 UTC
Created attachment 1485125 [details]
engine log with ERROR message

Error is written in log, but user don't get any hints in UI, neither in form of pop-up or at least some event.

Comment 3 Martin Perina 2018-09-21 09:38:11 UTC
Ravi, could you please take a look? According to logs Pavol attached:

1. Host upgrade was started

2018-09-20 14:34:57,963+02 INFO  [org.ovirt.engine.core.bll.hostdeploy.UpgradeHostCommand] (default task-10) [da4f73e0-ebe9-4f78-a6ec-5b6006c430a5] Running command: UpgradeHostCommand internal: false. Entities affected :  ID: 14169f6a-a596-4dea-b175-aa3b8a6761d9 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN
2018-09-20 14:34:58,079+02 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-10) [] EVENT_ID: HOST_UPGRADE_STARTED(840), Host vhost2 upgrade was started (User: admin@internal-authz).


2. MaintenanceNumberOfVdssCommand command during validation phase due to pinned VMs

2018-09-20 14:34:58,132+02 ERROR [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [da4f73e0-ebe9-4f78-a6ec-5b6006c430a5] VDS '14169f6a-a596-4dea-b175-aa3b8a6761d9' contains non migratable VMs
2018-09-20 14:34:58,132+02 WARN  [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [da4f73e0-ebe9-4f78-a6ec-5b6006c430a5] Validation of action 'MaintenanceNumberOfVdss' failed for user admin@internal-authz. Reasons: VAR__TYPE__HOST,VAR__ACTION__MAINTENANCE,VDS_CANNOT_MAINTENANCE_IT_INCLUDES_NON_MIGRATABLE_VM,$VmsList ddd,$HostsList vhost2

3. But above error was not propagated to UpgradeHostCommand and there's also not UpgradeHostCommand finished message in audit_log

Comment 4 Petr Matyáš 2018-12-04 13:24:56 UTC
Using ovirt-engine-4.2.8-0.1.el7ev.noarch I still don't see any message after upgrade started event and log appears the same as in comment#3

Comment 5 Petr Matyáš 2019-01-10 16:49:43 UTC
Verified on ovirt-engine-4.2.8.2-0.1.el7ev.noarch

Comment 6 Sandro Bonazzola 2019-01-22 10:23:41 UTC
This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019.

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