Bug 2258481

Summary:	default cpu_mode set as host-passthrough in ComputeResource Libvirt
Product:	Red Hat Satellite	Reporter:	Gaurav Talreja <gtalreja>
Component:	Compute Resources - libvirt	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.15.0	CC:	ekohlvan, rlavi, sganar
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:41:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gaurav Talreja 2024-01-15 15:55:46 UTC

Description of problem:
default cpu_mode set as host-passthrough in ComputeResource Libvirt after fix in https://bugzilla.redhat.com/show_bug.cgi?id=2236693

Version-Release number of selected component (if applicable):
Satellite 6.15.0 Snap 5.0

How reproducible:
Always

Steps to Reproduce:
1. Prepare Satellite for provisioning, and setup Libvirt CR
2. Sync content and kickstart repos, publish CV, create AK
3. Provision a host on Libvirt CR with cpu_mode as default

Actual results:
default cpu_mode set as host-passthrough on ComputeResource Libvirt

Expected results:
default cpu_mode set as "custom (qemu64)" earlier on ComputeResource Libvirt

Additional info:
Found this while testing this BZ and @ekohlvan suggested to drop this option altogether
upstream discussion - https://community.theforeman.org/t/drop-cpu-type-option-from-libvirt-compute-resource-provisioning/36267

Comment 2 Eric Helms 2024-06-06 16:41:05 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.