Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

Bug 1676865

Summary: building grub2 provisioning template for ppc64le system have "linuxefi" and "initrdefi" instead of "linux" and "initrd"
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Provisioning TemplatesAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: egolov, lzap, mhulan
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.22.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 19:47:10 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:
Attachments:
Description Flags
pxe loader options none

Description Jan Hutař 2019-02-13 12:38:27 UTC
Description of problem:
building grub2 provisioning template for ppc64le system have "linuxefi" and "initrdefi" instead of "linux" and "initrd"


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


How reproducible:
always


Steps to Reproduce:
1. Sync and configure RHEL8 for ppc64le and create a ppc64le host
2. [root@satellite ~]# cat /var/lib/tftpboot/grub2/grub.cfg-01-52-54-00-03-6c-3a
# This file was deployed via 'Kickstart default PXEGrub2' template


set default=0
set timeout=10

menuentry 'Kickstart default PXEGrub2' {
  linuxefi boot/jhutar-rhel8-8-0-ppc64le-baseos-HTHEmef4Z_-vmlinuz ks=http://satellite.nodhcp.local:8000/unattended/provision?token=0c66d7a2-9669-436e-bf78-566aa31eaed6  network ksdevice=bootif ks.device=bootif BOOTIF=00-52-54-00-03-6c-3a kssendmac ks.sendmac inst.ks.sendmac BOOTIF=01-$net_default_mac
  initrdefi boot/jhutar-rhel8-8-0-ppc64le-baseos-HTHEmef4Z_-initrd.img
}


Actual results:
There is "linuxefi" and "initrdefi" instead of "linux" and "initrd"


Expected results:
There should be "linux" and "initrd"

Comment 1 Bryan Kearney 2019-03-05 21:05:41 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26051 has been resolved.

Comment 4 Roman Plevka 2019-09-10 11:02:43 UTC
Created attachment 1613547 [details]
pxe loader options

Comment 5 Roman Plevka 2019-09-10 14:58:29 UTC
VERIFIED
on sat6.6.0-19

linuxefi and initrdefi are only generated for UEFI loaders.
RHEL<7 || non-uefi loaders properly generate "linux" and "initrd" lines.

Comment 6 Bryan Kearney 2019-10-22 19:47:10 UTC
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://access.redhat.com/errata/RHSA-2019:3172