View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016019||CentOS-7||-OTHER||public||2019-04-18 16:50||2019-04-18 20:43|
|Priority||normal||Severity||major||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0016019: package OVMF-20180508-3.gitee3198e672e2.el7 removed file OVMF_CODE.fd from previous version|
|Description||The previous version of the OVMF package (which supplies a UEFI bootloader for virtual machines) provided files OVMF_CODE.fd and OVMF_VARS.fd.|
The new version of the package adds OVMF_VARS.secboot.fd and OVMF_CODE.secboot.fd but then *removes* OVMF_CODE.fd. This will break existing virtual machines that specified the use of OVMF_CODE.fd as the bootloader.
For comparison, the equivalent Fedora package includes both OVMF_CODE.fd and OVMF_CODE.secboot.fd.
It seems this exclusion was explicit, the spec file in the srpm contains this:
|Steps To Reproduce||boot an instance using UEFI using OVMF-20150414-2.gitc9e5618.el7.noarch.rpm. stop the instance. upgrade to OVMF-20180508-3.gitee3198e672e2.el7.noarch.rpm, try to start the instance.|
|Tags||No tags attached.|
|As said on IRC, you need to check on RHEL to see if this is true there. If it is true then it's by design and CentOS just follows after and it's not our bug. If it's still in RHEL then it is a CentOS bug.|
|Okay, I've confirmed that it's also true on RHEL.|
|Ok, so that means it's what's called an upstream bug (if it is) and you'll have to report it on bugzilla.redhat.com to stand a chance of getting it either fixed or answered. If/when RH accepts it as a bug and incorporates a fix into RHEL and releases the patched version, then CentOS will pick it up and rebuild it.|