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 1492285

Summary: unknown keyword in configuration file: IPAPPEND on console while booting host w/ static IP full host bootdisk
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: Bootdisk PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.3.0CC: bbuckingham, lzap, mhulan
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-13 08:26:00 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
unknown keyword in configuration file: IPAPPEND none

Description Sachin Ghai 2017-09-16 06:15:51 UTC
Created attachment 1326673 [details]
unknown keyword in configuration file: IPAPPEND

Description of problem:

I was testing out full host bootdisk w/ static IP and found that when we
boot the host w/ bootdisk, an error appeared on screen as :

unknown keyword in configuration file: IPAPPEND


its not affecting the overall provisioning but appears while booting the host w/ ISO. 

here is the preview pf PXELinux template:
=======================================


# This file was deployed via 'Kickstart default PXELinux' template


TIMEOUT 10
DEFAULT Kickstart default PXELinux

LABEL Kickstart default PXELinux
  KERNEL boot/RedHat-7.4-x86_64-vmlinuz
  APPEND initrd=boot/RedHat-7.4-x86_64-initrd.img ks=http://SAT_SERVER/unattended/provision?token=0436500f-61a9-4140-81b5-348a75e16c0c  network ksdevice=bootif ks.device=bootif BOOTIF=00-52-54-00-85-88-36 kssendmac ks.sendmac inst.ks.sendmac ip=192.168.100.101::192.168.100.1:255.255.255.0:::none nameserver=192.168.100.1
  IPAPPEND 2



Version-Release number of selected component (if applicable):
sat6.3 snap15

How reproducible:


Steps to Reproduce:
1. boot the host w/ static IP full host bootdisk
2.
3.

Actual results:

on booting the host w/ bootdisk ISO: unknown keyword in configuration file: IPAPPEND


Expected results:
no error should be there

Additional info:

Comment 2 Lukas Zapletal 2017-09-18 08:18:23 UTC
So I took a closer look on this, IPAPPEND is a statement which is not recognized in SYSLINUX older than 5.10.

In both RHEL6 and RHEL7 there is SYSLINUX version 4.0x therefore this warning is expected.

https://access.redhat.com/downloads/content/syslinux/4.05-13.el7/x86_64/fd431d51/package

I suggest to put this on backlog but there is no work associated, after SYSLINUX is rebased in RHEL this will disappear. Bootdisk does not need the IPAPPEND 2 option at all, we might want to remove it.

Comment 3 Marek Hulan 2017-11-10 07:40:00 UTC
Is that tracked upstream? It should be linked or cloned when marked as devel triaged. Also I changed the component, tje template should be updated in bootdisk right?