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

Bug 2118672

Summary:	Use rpm instead of auto in package_facts ansible module to prevent mistakes of determining the correct package manager inside package_facts module
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Shruti <skavishw>
Component:	ovirt-engine	Assignee:	Dana <delfassy>
Status:	CLOSED NEXTRELEASE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.5.1	CC:	klaas, mperina
Target Milestone:	ovirt-4.5.3
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.3	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-19 14:31:24 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:

Comment 1 Martin Perina 2022-08-17 11:30:11 UTC

So not sure why apt is installed on RHEL hosts, it shouldn't be installed by default. But we can override the automatic package manager identification inside package_facts module, by using 'manager: rpm' as RHV supports only RHVH or RHEL-H hypervisors.

Comment 2 Klaas Demter 2022-08-25 08:20:47 UTC

Hi,
I'd say it's not a bug in rhv/ovirt, it's a bug in ansible for mistaking apt binary without checking if it's actually the apt package manager.
About workarounds, I don't think we actually need java installed on the rhel hypervisors, so I am recommending internally to just remove the package.
None the less I still think this is something that should at addressed in ansible if it's also happening outside of rhv/ovirt (I did not test that). Otherwise you can't install java and use ansible at the same time on rhel(or other rpm/yum/dnf) hosts.

Greetings
Klaas

Comment 3 Casper (RHV QE bot) 2022-09-11 13:30:59 UTC

This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).

Comment 6 Casper (RHV QE bot) 2022-09-19 14:31:24 UTC

This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.