Bug 1795184

Summary: Check for upgrade on RHEL 8 host always reports no updates
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: ovirt-host-deploy-ansibleAssignee: Dana <delfassy>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, mperina
Target Milestone: ovirt-4.4.0Keywords: Regression
Target Release: ---Flags: pm-rhel: ovirt-4.4+
pm-rhel: blocker?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:01:19 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: 1715763    

Description Petr Matyáš 2020-01-27 11:49:13 UTC
Description of problem:
I have a RHEL 8 host in my 4.4 setup and it reports no updates even though I have update for couple packages (e.g. vdsm)

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0-0.17.master.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. have a host on RHEL 8 with updates for any packages (vdsm seems like a good candidate)
2. run check or updates
3.

Actual results:
no updates found

Expected results:
updates found

Additional info:
format of the return message of yum update is different from RHEL 7 so maybe that is the issue here?

I don't really see anything in logs, so just ask for specific logs you need.

2020-01-27 12:40:09,205+01 INFO  [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand] (EE-ManagedExecutorService-com
mandCoordinator-Thread-1) [0538aed4-b4c7-4b77-b18f-a25a7154a8ef] Running command: HostUpgradeCheckInternalCommand internal: true. Enti
ties affected :  ID: 6c26d23b-5912-420b-b6ad-2ddd8c1041cc Type: VDS
2020-01-27 12:40:09,248+01 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-2) [] EVENT_ID:
HOST_AVAILABLE_UPDATES_STARTED(884), Started to check for available updates on host dell-r210ii-14.
2020-01-27 12:40:30,494+01 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedExecutorService-com
mandCoordinator-Thread-1) [0538aed4-b4c7-4b77-b18f-a25a7154a8ef] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Check for update of
 host dell-r210ii-14. Gathering Facts.
2020-01-27 12:40:39,788+01 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedExecutorService-com
mandCoordinator-Thread-1) [0538aed4-b4c7-4b77-b18f-a25a7154a8ef] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Check for update of
 host dell-r210ii-14. Install ovirt-host package if it isn't installed.
2020-01-27 12:40:46,022+01 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedExecutorService-com
mandCoordinator-Thread-1) [0538aed4-b4c7-4b77-b18f-a25a7154a8ef] EVENT_ID: ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Check for update of
 host dell-r210ii-14. Update system.
2020-01-27 12:40:52,343+01 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedExecutorService-com
mandCoordinator-Thread-1) [0538aed4-b4c7-4b77-b18f-a25a7154a8ef] EVENT_ID: HOST_AVAILABLE_UPDATES_FINISHED(885), Check for available u
pdates on host dell-r210ii-14 was completed successfully with message 'no updates found.'.

Comment 1 RHEL Program Management 2020-01-27 11:54:58 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Petr Matyáš 2020-03-20 10:02:52 UTC
Verified on ovirt-engine-4.4.0-0.25.master.el8ev.noarch

Comment 3 Sandro Bonazzola 2020-05-20 20:01:19 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

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