Bug 1889851

Summary:	Facing issue while upgrading RHEL(7.9) based SHE hypervisor
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	nsurati
Component:	ovirt-host-deploy	Assignee:	Martin Perina <mperina>
Status:	CLOSED NEXTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.11	CC:	cshao, dougsland, lsurette, mhicks, michal.skrivanek, mtessun, pelauter, srevivo
Target Milestone:	ovirt-4.4.3
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:	2020-11-13 08:24:06 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 nsurati 2020-10-20 17:22:41 UTC

Description of problem:

Facing issue while upgrading RHEL(7.9) based SHE hypervisor because of higher version of ansible package available

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Upgrade failed because of higher version of ansible package available  

Expected results:

Upgrade Host without any issue

Additional info:

Comment 2 Michal Skrivanek 2020-10-21 04:25:57 UTC

You can also disable the ansible repository

Comment 3 Martin Perina 2020-11-13 08:24:06 UTC

This issue has been fixed in RHV 4.4.3, no further release of RHV Manager 4.3 are planned, so customers just need to workaround mentioned in https://access.redhat.com/solutions/5480561

Comment 4 peyu 2021-01-20 04:43:13 UTC

Does this issue occur during host upgrade or engine upgrade? What does SHE mean?
Could you please give me a detailed step to reproduce this issue? Thank you.

Comment 5 nsurati 2021-02-03 06:11:45 UTC

You may close the Bugzilla. 

First issue faced while upgrading self hosted engine host (SHE Host) but later it identified that issue same mentioned in https://access.redhat.com/solutions/5480561

Comment 6 cshao 2021-04-22 02:57:50 UTC

According #c3 and #c5, customers just need to workaround mentioned in https://access.redhat.com/solutions/5480561.