Bug 1663242

Summary: Check for update on host doesn't work with dnf installed
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.InfraAssignee: Martin Necas <mnecas>
Status: CLOSED WONTFIX QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: bugs, mperina, omachace
Target Milestone: ---Flags: sbonazzo: ovirt-4.4-
aoconnor: blocker-
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: 2019-10-09 14:35:27 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:    
Bug Blocks: 1668685    

Comment 1 Sandro Bonazzola 2019-01-23 09:56:18 UTC
Any plan to get this fixed in 4.3? dnf is already available in el7.6 and nothing currently prevent it to be installed there.

Comment 2 Ondra Machacek 2019-01-25 07:39:44 UTC
There are actually two issues, first that dnf Ansible module don't report correct state, when using update_cache:yes. And the second is that it doesn't report packages which will be installed/updated/removed, when using check-model. We need to get this fixed in Ansible DNF module.

Comment 5 Martin Perina 2019-02-25 14:21:36 UTC
Moving to 4.4 due to capacity, but we will try to get that fixed in 4.3.z

Comment 6 Martin Necas 2019-10-09 12:11:37 UTC
I was not able to reproduce this issue with ansible 2.8.1 and Centos 7.6.1810.

Comment 7 Petr Matyáš 2019-10-09 14:13:37 UTC
Well yeah, now it uses hardcoded yum. So even with dnf installed it will still use yum.

Comment 8 Martin Necas 2019-10-09 14:35:27 UTC
Now is everything working on yum, only reason for any change in ansible role would be if yum would become deprecated.