-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.15.0, 6.16.0, 6.17.0
-
8
-
False
-
Moderate
-
sat-rocket
-
None
-
None
-
None
-
To Do
Description of problem:
Whether creating a compute profile by selecting the firmwire as UEFI or BIOS or creating it by selecting as BIOS and later updating it to UEFI, perhaps saves the compute profile data at the backend correctly but if we edit the compute-profile back in UI, we see "Automatic" is selected as the firmware type.
How reproducible:
Always
Is this issue a regression from an earlier version:
Perhaps
Steps to Reproduce:
1. Install a satellite 6.16
2. Create a VMware compute resource
3. Create a Compute Profile using that Compute Resource, having Firmware selected as UEFI.
4. Edit back the Compute Profile to check the saved value of Firmware
Actual behavior:
In Step 3:
Logs:
2025-03-03T19:35:16 [I|app|3259ef57] Started POST "/compute_profiles/5-Sat-RH9-UEFI/compute_attributes" for x.x.x.x at 2025-03-03 19:35:16 +0530 2025-03-03T19:35:16 [I|app|3259ef57] Processing by ComputeAttributesController#create as HTML 2025-03-03T19:35:16 [I|app|3259ef57] Parameters: {"authenticity_token"=>"kgRRqmX_jc7ogBSl3k6GrkXVSFxuPETo2UoAtTBt9W8IPEteOVcidskXMb3WMpkqeSWXM5nrMsz_16z0nRWEGA", "compute_attribute"=>{"vm_attrs"=>{"cpus"=>"1", "corespersocket"=>"1", "memory_mb"=>"4096", "firmware"=>"uefi", "cluster"=>"SYSLAB", "resource_pool"=>"Resources", "path"=>"/Datacenters/PRIME/vm/SYSMGMT/saydas", "guest_id"=>"rhel9_64Guest", "hardware_version"=>"Default", "memoryHotAddEnabled"=>"1", "cpuHotAddEnabled"=>"1", "add_cdrom"=>"0", "boot_order"=>["network", "disk"], "annotation"=>"", "virtual_tpm"=>"0", "controllers"=>"{\"controllers\":[{\"type\":\"ParaVirtualSCSIController\",\"key\":1000}],\"volumes\":[{\"thin\":true,\"name\":\"Hard disk\",\"mode\":\"persistent\",\"sizeGb\":10,\"controllerKey\":1000,\"datastore\":\"Arcade\",\"storagePod\":null}]}", "interfaces_attributes"=>{"0"=>{"type"=>"VirtualVmxnet3", "network"=>"dvportgroup-853"}}}, "compute_profile_id"=>"5", "compute_resource_id"=>"1"}, "commit"=>"Submit", "compute_profile_id"=>"5-Sat-RH9-UEFI"} 2025-03-03T19:35:17 [I|aud|3259ef57] ComputeAttribute (2) create event on compute_profile_id 5 2025-03-03T19:35:17 [I|aud|3259ef57] ComputeAttribute (2) create event on compute_resource_id 1 2025-03-03T19:35:17 [I|aud|3259ef57] ComputeAttribute (2) create event on name 1 CPUs and 4096 MB memory 2025-03-03T19:35:17 [I|aud|3259ef57] ComputeAttribute (2) create event on vm_attrs {"cpus"=>"1", "corespersocket"=>"1", "memory_mb"=>"4096", "firmware"=>"uefi", "cluster"=>"SYSLAB", "resource_pool"=>"Resources", "path"=>"/Datacenters/PRIME/vm/SYSMGMT/saydas", "guest_id"=>"rhel9_64Guest", "hardware_version"=>"Default", "memoryHotAddEnabled"=>"1", "cpuHotAddEnabled"=>"1", "add_cdrom"=>"0", "boot_order"=>["network", "disk"], "annotation"=>"", "virtual_tpm"=>"0", "interfaces_attributes"=>{"0"=>{"type"=>"VirtualVmxnet3", "network"=>"dvportgroup-853"}}, "volumes_attributes"=>{"0"=>{"thin"=>true, "name"=>"Hard disk", "mode"=>"persistent", "size_gb"=>10, "controller_key"=>1000, "datastore"=>"Arcade", "storage_pod"=>nil}}, "nvme_controllers"=>[], "scsi_controllers"=>[{"type"=>"ParaVirtualSCSIController", "key"=>1000}]} 2025-03-03T19:35:17 [I|app|3259ef57] Redirected to https://satellite-fqdn/compute_profiles/5-Sat-RH9-UEFI 2025-03-03T19:35:17 [I|app|3259ef57] Completed 302 Found in 250ms (ActiveRecord: 58.3ms | Allocations: 18388)
hammer output:
# hammer compute-profile info --id 5
Id: 5
Name: Sat-RH9-UEFI
Created at: 2025/03/03 14:04:40
Updated at: 2025/03/03 14:04:40
Compute attributes:
1) Id: 2
Name: 1 CPUs and 4096 MB memory
Compute Resource: Optimus
VM attributes: {"cpus"=>"1", "corespersocket"=>"1", "memory_mb"=>"4096", "firmware"=>"uefi", "cluster"=>"SYSLAB", "resource_pool"=>"Resources", "path"=>"/Datacenters/PRIME/vm/SYSMGMT/saydas", "guest_id"=>"rhel9_64Guest", "hardware_version"=>"Default", "memoryHotAddEnabled"=>"1", "cpuHotAddEnabled"=>"1", "add_cdrom"=>"0", "boot_order"=>["network", "disk"], "annotation"=>"", "virtual_tpm"=>"0", "interfaces_attributes"=>{"0"=>{"type"=>"VirtualVmxnet3", "network"=>"dvportgroup-853"}}, "volumes_attributes"=>{"0"=>{"thin"=>true, "name"=>"Hard disk", "mode"=>"persistent", "size_gb"=>10, "controller_key"=>1000, "datastore"=>"Arcade", "storage_pod"=>nil}}, "nvme_controllers"=>[], "scsi_controllers"=>[{"type"=>"ParaVirtualSCSIController", "key"=>1000}]}
As we can see the firmware type was set to UEFI during creation and hammer reflects so.
On Step 4, But if you edit the CP in WebUI, the type is set to Automatic ( see screenshot for more details )
Expected behavior:
WebUI and CLI should display the correct and consistent values for compute profiles.
Business Impact / Additional info:
UX Impact
- is duplicated by
-
-
- Closed
-
