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.

Bug 1350411

Summary: fcoe: anaconda is eating newlines when creating fcoe device config file from cfg-ethx example template
Product: Red Hat Enterprise Linux 7 Reporter: Radek Vykydal <rvykydal>
Component: python-blivetAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: mhruscak
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-blivet-0.61.15.55-1 Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 23:53:23 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:

Description Radek Vykydal 2016-06-27 11:40:29 UTC
The fcoe config file for NIC is created using /etc/fcoe/eth-cfgx example config file by replacing relevant lines with configured values.
It is eating newlines of the value lines during the process. For example:

original eth-cfgx:
<snip>
## Type:       yes/no
## Default:    no
# Indicate if DCB service is required at the Ethernet port
# Normally set to "yes"
DCB_REQUIRED="yes"

## Type:|_______yes/no
## Default:|____no
# Indicate if VLAN discovery should be handled by fcoemon
# Normally set to "yes"
AUTO_VLAN="yes"
</snip>

becomes:

<snip>
## Type:       yes/no
## Default:    no
# Indicate if DCB service is required at the Ethernet port
# Normally set to "yes"
DCB_REQUIRED="no"
## Type:|_______yes/no
## Default:|____no
# Indicate if VLAN discovery should be handled by fcoemon
# Normally set to "yes"
AUTO_VLAN="yes"
</snip>

when setting DCB_REQUIRED value, note removing the blank line after DCB_REQUIRED="no".

The config file is still valid due to additional newline in the original eth-cfgx but it may change in the future.

Comment 1 Radek Vykydal 2016-06-27 11:45:21 UTC
https://github.com/rhinstaller/blivet/pull/448

Comment 4 Marek Hruscak 2016-09-05 12:41:37 UTC
Verified on RHEL-7.3-20160901.1 with anaconda-21.48.22.86-1

New lines in /etc/fcoe/eth-cfgx configs are not eaten anymore so generated file adheres to convention defined in example file.

Comment 5 Marek Hruscak 2016-09-05 12:43:37 UTC
*with python-blivet-0.61.15.55-1

Comment 7 errata-xmlrpc 2016-11-03 23:53:23 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://rhn.redhat.com/errata/RHBA-2016-2168.html