Bug 1786772

Summary: Task Update system failed to execute - Running QEMU processes found, cannot upgrade Vdsm
Product: [oVirt] ovirt-engine Reporter: Alexander Murashkin <alexandermurashkin>
Component: Host-DeployAssignee: Dana <delfassy>
Status: CLOSED WORKSFORME QA Contact: Lukas Svaty <lsvaty>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, dfediuck, didi, mperina
Target Milestone: ovirt-4.4.0Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-16 09:55:57 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 and host logs and packages none

Description Alexander Murashkin 2019-12-27 21:51:30 UTC
Created attachment 1648147 [details]
Engine and host logs and packages

Description of problem:

On a regular basis, there is "Task Update system failed to execute" error in the engine.log. At the same time, the ovirt-host-mgmt-ansible-check log contains "Running QEMU processes found, cannot upgrade Vdsm" error. It can be reproduced it easily. 

If no virtual machines are running, Host -> Installation -> Check for upgrade returns "no updates found".

If there are virtual machines running, Host -> Installation -> Check for upgrade returns "failed to check for available updates..."

Version-Release number of selected component (if applicable):

    Engine  ovirt-engine-tools-4.4.0-0.0.master.20191222221018.gitc154119.el7.noarch
    Host    vdsm-4.40.0-1436.git6e7278919.el8.x86_64

Actual results:

    failed to check for available updates... event

Expected results:

    no updates found event, no matter if the virtual machines are running

Additional info:

See the attached logs and package lists.

Comment 1 RHEL Program Management 2019-12-31 06:46:15 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Dana 2020-02-27 12:01:21 UTC
I wasn't able to reproduce, but posted a fix that might resolve this issue
Let me know if it still occurs

Comment 3 Martin Perina 2020-03-16 09:55:57 UTC
Closing as worksforme, feel free to reopen if you are able to reproduce and attach all logs and reproducing steps

Comment 4 Red Hat Bugzilla 2023-09-14 05:49:15 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days