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:
ifup fails, but claims to succeed.
This issue is a reproduction of BZ 1183728, but out of oVirt.

Version-Release number of selected component (if applicable):
initscripts-9.49.17-1.el7_0.1.x86_64
3.5.0-0.29.el6ev

Red Hat Enterprise Linux Server release 7.0 (Maipo)

How reproducible:
100

Steps to Reproduce:
1. Define ifcfg-bond0(2 slaves) with MTU 50000 (custom MTU that is not supported by host)
2. ifup bond0
3. Check if proper bond0 is created

Actual results:
Proper bond0 doesn't created, bond0 is broken, there is no slaves.
and ends without error.

cat /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
BONDING_OPTS='mode=4 miimon=100'
ONBOOT=no
NM_CONTROLLED=no
HOTPLUG=no
MTU=50000

echo $?  (after ifup bond0 command)
0

cat /sys/class/net/bond0/bonding/slaves
empty

cat /sys/class/net/bond0/
no slaves

ip a
bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 50000 qdisc noqueue state DOWN

Expected results:
ifup command should succeed, and if not, then should be a proper error about this.

Additional info:
See also-  https://bugzilla.redhat.com/show_bug.cgi?id=1183728

When you have bond interface you expect that some of the slaves may fail and it is still OK, or they could be activated later. We can't change that behavior.

We could add a warning message, but that won't probably help in your case.

In Michael's case, *none* of the slaves were activated. In my opinion, this should be considered an error case.

After some thinking, I have just added the warning message. The bond gets up just fine, the fact that it does not have any slave is something different (they could be added for example by hand later.)

https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel7-branch&id=8fd278b052b0e4882887c393a102dd453803b477

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-2015-2134.html