This occurs when you have previously used ovftool/powershell to import ovf file into vCenter , and when it is downloaded and re-imported again.
This will be fixed in an upcoming release.
You can use Powershell with PowerCLi to complete the task ,Make sure to replace the placeholders with the appropriate paths and names for your specific environment
# Connect to your vCenter server
Connect-VIServer -Server <vCenter_Server> -User <Username> -Password <Password>
# Set the path to the OVF file
$ovfPath = "C:\Users\Downloads\test\centos.ovf"
# Set the target location for the imported virtual machine
$VMHost = Get-Cluster | Get-VMHost | ?{$_.ConnectionState -eq "Connected"} | Get-Random
$Datastore = Get-Datastore -Name "vsanDatastore"
# Import the OVF file
Import-VApp -VMHost $VMHost -Datastore $Datastore -Source $ovfPath -Name centos