Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If Product in /.buildinfo does not start with "Red Hat" (RHEV-H, for example), Anaconda will pick /fedora as the EFI path, as it has the highest priority.
Version-Release number of selected component (if applicable):
anaconda 21.48.22.56-1
How reproducible:
100%
Steps to Reproduce:
Change "Product" in /.buildinfo to start with anything other than "Red Hat"
Actual results:
"Fedora" has the highest priority
Expected results:
RHEV (and probably other variants) should be identified as RHEL, or have a way to override it other than changing the product. It's ok if this can be set with an additional field, to force selection to one of Fedora/CentOS/RHEL or other supported variants.
This has a direct impact on EFI support, because the EFI loader location is determined by the install class, and the paths are different between RHEL and Fedora
I think it is much cleaner for products to identify themselves as "Red Hat ..." than it is for us to have to maintain a list of all the possible naming conventions that may come up.
I agree, but "Red Hat Enterprise Virtualization Hypervisor" is a bit long for the Anaconda GTK interface.
The ability to override it (in upstream Anaconda) would also be ideal for oVirt, as those images are based off of CentOS, but tying the naming to "CentOS ..." or "Fedora ..." doesn't really work from an oVirt product perspective.
I think we need to separate this bug, because there are two issues:
1. anaconda identifies RHEL/CentOS/Fedora based on the product title
2. anaconda screen exceeds display width it the title is to long (bug 1338793)
As there is a bug for 2., I'd suggest that we discuss 1. here.
It has to be considered that this bug becomes less relevant if bug 1338793 is getting fixed.
Because currently we need to choose a short title i.e. RHEV-H 3.6 Tech Preview, in which case anaconda falsely detects Fedora - which in turn breaks EFI (because the EFI path depends on the product).
Thoughts?
I think the right way to do that would be to make, and maintain, your own rhev.py installclass and install it with a product.img or additional package when you create your live image.
Right, we are actually rather at aiming to upstream our (very few) changes - the installclass is probably the only real change.
All other related changes are bugs which QE found in our flows, but which are in anaconda.
Do you have obejctions on including it in upstream?
(In reply to Fabian Deutsch from comment #7)
> Right, we are actually rather at aiming to upstream our (very few) changes -
> the installclass is probably the only real change.
>
> All other related changes are bugs which QE found in our flows, but which
> are in anaconda.
>
> Do you have obejctions on including it in upstream?
I do, yes, but that's probably a final decision for sbueno.
Comment 12Samantha N. Bueno
2016-09-08 15:26:36 UTC
Patch is on review: https://github.com/rhinstaller/anaconda/pull/776
Setting this to POST.
I spoke to dougsland who said that the RHEV-H QE team can test for this specific fix, so RTT you can set this OtherQA.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2158.html