Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1662637

Summary:	Failure to run "check-for-update" in the web UI after upgrade
Product:	[oVirt] ovirt-engine	Reporter:	Liran Rotenberg <lrotenbe>
Component:	General	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Liran Rotenberg <lrotenbe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs, mavital, mperina
Target Milestone:	---
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-01-21 12:39:14 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:

Description Liran Rotenberg 2018-12-31 09:00:49 UTC

Description of problem:
After upgrading the engine from 4.2.8 to 4.3, trying to use "Check for upgrade" from the engine's web UI failed.
"Failed to check for available updates on host host_mixed_1 with message 'Failed to run check-update of host <HOST>.'"

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0-0.6.alpha2.el7.noarch
# rpm -qa | grep ansible
ovirt-ansible-v2v-conversion-host-1.8.0-1.el7ev.noarch
ovirt-ansible-disaster-recovery-1.1.3-1.el7ev.noarch
ovirt-ansible-hosted-engine-setup-1.0.2-1.el7ev.noarch
ansible-2.7.5-1.el7ae.noarch
ovirt-ansible-shutdown-env-1.0.0-1.el7ev.noarch
ovirt-ansible-image-template-1.1.9-1.el7ev.noarch
ovirt-ansible-manageiq-1.1.13-1.el7ev.noarch
ovirt-ansible-engine-setup-1.1.6-1.el7ev.noarch
ovirt-ansible-cluster-upgrade-1.1.9-1.el7ev.noarch
ovirt-ansible-repositories-1.1.3-1.el7ev.noarch
ovirt-ansible-infra-1.1.10-1.el7ev.noarch
ovirt-ansible-vm-infra-1.1.12-1.el7ev.noarch
ovirt-ansible-roles-1.1.6-1.el7ev.noarch

How reproducible:
Once(on SHE), didn't try to reproduce.

Steps to Reproduce:
1. Have 4.2.8 setup.
2. Upgrade the engine to 4.3.
3. Run from web UI: Compute->Hosts->select host->Installation->Check for upgrade.

Actual results:
Check for upgrade failed with:
"Failed to check for available updates on host host_mixed_1 with message 'Failed to run check-update of host <HOST>.'"

Expected results:
Check for upgrade should pass.

Additional info:
Reinstalling the host (Host->Maintenance->Reinstall) seem to fix it.

Comment 2 Martin Perina 2019-01-21 12:39:14 UTC


*** This bug has been marked as a duplicate of bug 1658544 ***