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.
DescriptionStefan Nordhausen
2015-04-10 12:56:30 UTC
Description of problem:
We auto-generate the network config for all our hosts. After a change in the auto-generation tool, config items now look like
NETMASK='255.255.255.255.0'
i.e. they use single quotes. This works fine since the network scripts will use the "source" command to include the configs. So any valid shell syntax will do the job.
The only exception is the MASTER variable in the configuration files of ethernet devices when a bonding is configured. This is because /etc/sysconfig/network-scripts/ifup-eth uses the code
for device in $(LANG=C grep -l "^[[:space:]]*MASTER=\"\?${DEVICE}\"\?\([[:space:]#]\|$\)" /etc/sysconfig/network-scripts/ifcfg-*) ; do
to find the individual devices for a bond. Note that the regular expression accepts double quotes or no quotes, but not single quotes. Essentially, the regular expression tries to parse shell scripts, which is not trivial. It sounds like a better idea to let the shell parse the shell script:
for device in /etc/sysconfig/network-scripts/ifcfg-*; do
if [ $(source $config; echo -n $MASTER) == ${DEVICE} ]; then
This will work for any kind of quoting, escaping or other strange stuff that is valid shell syntax.
A very similar issue exists in the ifdown-eth script.
How reproducible:
100%
Steps to Reproduce:
1. Configure a bond of 2 Ethernet NICs.
2. Change the quoting around the MASTER variable in /etc/sysconfig/network-scripts/ifcfg-eth* to use single quotes like
MASTER='bond0'
3. After "service network restart", the bond does not work.
/etc/sysconfig/network-scripts/ifup-eth is part of initscripts.
NetworkManger is not involved here. Reassigning bug.
Note that NetworkManagers ifcfg-rh plugin also reads /etc/sysconfig/network-scripts/ifcfg-* and also would not understand complex configuration files.
Especially, it would not spawn a shell to parse the config files.
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-0951.html
Description of problem: We auto-generate the network config for all our hosts. After a change in the auto-generation tool, config items now look like NETMASK='255.255.255.255.0' i.e. they use single quotes. This works fine since the network scripts will use the "source" command to include the configs. So any valid shell syntax will do the job. The only exception is the MASTER variable in the configuration files of ethernet devices when a bonding is configured. This is because /etc/sysconfig/network-scripts/ifup-eth uses the code for device in $(LANG=C grep -l "^[[:space:]]*MASTER=\"\?${DEVICE}\"\?\([[:space:]#]\|$\)" /etc/sysconfig/network-scripts/ifcfg-*) ; do to find the individual devices for a bond. Note that the regular expression accepts double quotes or no quotes, but not single quotes. Essentially, the regular expression tries to parse shell scripts, which is not trivial. It sounds like a better idea to let the shell parse the shell script: for device in /etc/sysconfig/network-scripts/ifcfg-*; do if [ $(source $config; echo -n $MASTER) == ${DEVICE} ]; then This will work for any kind of quoting, escaping or other strange stuff that is valid shell syntax. A very similar issue exists in the ifdown-eth script. How reproducible: 100% Steps to Reproduce: 1. Configure a bond of 2 Ethernet NICs. 2. Change the quoting around the MASTER variable in /etc/sysconfig/network-scripts/ifcfg-eth* to use single quotes like MASTER='bond0' 3. After "service network restart", the bond does not work.