Bug 1663949

Summary: Can't check for update on host after upgrade of engine
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: Host-DeployAssignee: Tomasz Barański <tbaransk>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: urgent    
Version: ---CC: bugs, mperina, omachace, pmatyas, rbarry
Target Milestone: ovirt-4.3.0Keywords: Automation, AutomationBlocker, Regression
Target Release: ---Flags: rule-engine: ovirt-4.3+
rule-engine: blocker+
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-02-13 07:43:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
debug engine log none

Description Petr Matyáš 2019-01-07 11:13:09 UTC
Created attachment 1518963 [details]
debug engine log

Description of problem:
After upgrade of engine I'm unable to run check for upgrade with exception:
2019-01-07 12:57:35,736+02 DEBUG [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [9f0c4f5a-bea7-4863-9074-e7f728981068] Exception: java.lang.RuntimeException: Failed to run check-update of host 'lynx20..redhat.com'.
Caused by: java.lang.RuntimeException: Failed to run check-update of host 'lynx20..redhat.com'. at org.ovirt.engine.core.bll.host.HostUpgradeManager.checkForUpdates(HostUpgradeManager.java:59) [bll.jar:]

Check for update finishes successfully when run on host manually (finds updates)

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0-0.6.alpha2.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install latest 4.2
2. upgrade engine to 4.3
3. check for upgrade on host

Actual results:
failed to check for updates

Expected results:
check for updates finishes successfully

Additional info:

Comment 2 Ryan Barry 2019-01-16 16:52:18 UTC
Tomas, this appears to be a side effect of the encrypted console changes which probably requires a change to the specfile. Can you take a look?

Comment 11 Petr Matyáš 2019-01-30 14:55:53 UTC
Verified on ovirt-engine-4.3.0.2-0.1.el7.noarch

Comment 12 Sandro Bonazzola 2019-02-13 07:43:02 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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