Bug 2266672

Summary:	Firmware in the compute profile for VMware defaults to BIOS every time after its edited to any other firmware
Product:	Red Hat Satellite	Reporter:	sganar
Component:	Compute Resources - VMWare	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.15.0	CC:	chrobert, mhulan, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
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:	2024-06-06 17:24:57 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 sganar 2024-02-28 17:42:54 UTC

Description of problem:
Firmware in the compute profile for VMware defaults to BIOS every time after it's edited to any other firmware.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a VMware Compute Resource
2. Update any compute profile (for eg: 1-Small) and set Firmware to `Automatic`
3. Open that compute profile again 

Actual results:
The firmware is defaulted to `BIOS`

Expected results:
The firmware should remain where it was while updating the compute profile

Additional info:

Comment 1 Eric Helms 2024-06-06 17:24:57 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.