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 1583709 - RHEL 7.5 kickstart incorrectly configures bonding
Summary: RHEL 7.5 kickstart incorrectly configures bonding
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-29 14:07 UTC by Stijn Tintel
Modified: 2020-11-11 21:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-11 21:42:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
/tmp/anaconda.log (11.36 KB, text/plain)
2018-06-01 11:46 UTC, Stijn Tintel 		no flags Details
/tmp/ifcfg.log (17.44 KB, text/plain)
2018-06-01 11:46 UTC, Stijn Tintel 		no flags Details
/tmp/packaging.log (141.63 KB, text/plain)
2018-06-01 11:47 UTC, Stijn Tintel 		no flags Details
/tmp/program.log (44.71 KB, text/plain)
2018-06-01 11:47 UTC, Stijn Tintel 		no flags Details
/tmp/storage.log (132.67 KB, text/plain)
2018-06-01 11:47 UTC, Stijn Tintel 		no flags Details
/var/log/anaconda/syslog (278.55 KB, text/plain)
2018-06-01 12:41 UTC, Stijn Tintel 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4000641 0 Install None Why does Red Hat Enterprise Linux 7.6 kickstart installation not create bond interfaces properly? 2019-03-21 08:05:34 UTC

Description Stijn Tintel 2018-05-29 14:07:35 UTC 
Description of problem:
RHEL 7.5 kickstart incorrectly configures bonding


How reproducible:
Always

Steps to Reproduce:
1. Create kickstart config with "network  --bootproto=static --device=bond0 --gateway=192.168.122.1 --hostname=tme-5238 --ip=192.168.122.78 --nameserver=192.168.122.1 --netmask=255.255.255.0 --noipv6 --activate --bondopts=mode=active-backup,primary=eth0,primary_reselect=0 --bondslaves=eth0,eth1"
2. Use this kickstart file to install a RHEL7.5 machine
3.

Actual results:
[root@tme-5238 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:41:2f:18 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.157/24 brd 192.168.122.255 scope global noprefixroute dynamic eth0
       valid_lft 3396sec preferred_lft 3396sec
    inet6 fe80::5054:ff:fe41:2f18/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:7a:19:bc brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.176/24 brd 192.168.122.255 scope global noprefixroute dynamic eth1
       valid_lft 3403sec preferred_lft 3403sec
    inet6 fe80::5054:ff:fe7a:19bc/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 86:56:44:09:45:96 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.78/24 brd 192.168.122.255 scope global noprefixroute bond0
       valid_lft forever preferred_lft forever

[root@tme-5238 ~]# ip ro
default via 192.168.122.1 dev eth0 proto dhcp metric 100
default via 192.168.122.1 dev eth1 proto dhcp metric 101
default via 192.168.122.1 dev bond0 proto static metric 300
192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.157 metric 100
192.168.122.0/24 dev eth1 proto kernel scope link src 192.168.122.176 metric 101
192.168.122.0/24 dev bond0 proto kernel scope link src 192.168.122.78 metric 300

[root@tme-5238 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
# Generated by parse-kickstart
UUID="f7e97312-44a8-4be2-bc9b-6dae79fbce97"
NAME="Bond connection bond0"
BONDING_MASTER="yes"
DNS1="192.168.122.1"
IPADDR="192.168.122.78"
GATEWAY="192.168.122.1"
NETMASK="255.255.255.0"
BOOTPROTO="static"
BONDING_OPTS="mode=active-backup primary=eth0 primary_reselect=0"
DEVICE="bond0"
TYPE="Bond"
ONBOOT="yes"
IPV6INIT="no"

[root@tme-5238 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0_slave_1
# Generated by parse-kickstart
NAME="bond0 slave 1"
MASTER="f7e97312-44a8-4be2-bc9b-6dae79fbce97"
DEVICE="eth0"
TYPE="Ethernet"
ONBOOT="yes"
UUID="e8ec72fe-999f-4701-8080-a92d4d968403"

[root@tme-5238 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0_slave_2
# Generated by parse-kickstart
NAME="bond0 slave 2"
MASTER="f7e97312-44a8-4be2-bc9b-6dae79fbce97"
DEVICE="eth1"
TYPE="Ethernet"
ONBOOT="yes"
UUID="40782847-23ed-45cb-97be-81ffcf97b11a"

[root@tme-5238 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Generated by dracut initrd
NAME="eth0"
HWADDR="52:54:00:41:2f:18"
ONBOOT=yes
NETBOOT=yes
UUID="4376c0ab-93aa-4521-848b-1e4c0cf78623"
IPV6INIT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
DNS1="192.168.122.1"

[root@tme-5238 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Generated by dracut initrd
NAME="eth1"
HWADDR="52:54:00:7a:19:bc"
ONBOOT=yes
NETBOOT=yes
UUID="17ba4d5d-504c-4a32-9bea-09a6b52e23d7"
IPV6INIT=yes
BOOTPROTO=dhcp
TYPE=Ethernet
DNS1="192.168.122.1"


Expected results:
/etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth1 should not exist. They break the bond configuration.
Comment 2 Jiri Konecny 2018-05-30 08:52:52 UTC 
Could you please provide us logs from the installation as plain text files. You can find them in /tmp/*.log .

Thank you.
Comment 3 Stijn Tintel 2018-06-01 11:46:23 UTC 
Created attachment 1446664 [details]
/tmp/anaconda.log
Comment 4 Stijn Tintel 2018-06-01 11:46:49 UTC 
Created attachment 1446665 [details]
/tmp/ifcfg.log
Comment 5 Stijn Tintel 2018-06-01 11:47:13 UTC 
Created attachment 1446666 [details]
/tmp/packaging.log
Comment 6 Stijn Tintel 2018-06-01 11:47:34 UTC 
Created attachment 1446667 [details]
/tmp/program.log
Comment 7 Stijn Tintel 2018-06-01 11:47:51 UTC 
Created attachment 1446668 [details]
/tmp/storage.log
Comment 8 Radek Vykydal 2018-06-01 12:33:58 UTC 
Please attach also /tmp/syslog (or /var/log/anaconda/syslog from installed system).

The ifcfgs for eth0 and eth1 are created in installer initramfs stage where the network is configured for installation environment.

It is possible to configure the slave devices ifcfg-ethX files to be not applied after reboot on installed system by adding
network --device=eth0 --onboot=no
network --device=eth1 --onboot=no
to kickstart file (after the network command for the bond).

I am not sure if this should be done automatically by the installer. In general, we only add (or modify) the kickstart network configuration to the configuration coming from boot options. I'd need /tmp/syslog to see the used boot options.


Maybe NetworkManager or network service should resolve the ifcfg configuration by applying the bond configuration without applying the configuration from ifcfg-ethX to the slaves on the installed system.
Comment 9 Stijn Tintel 2018-06-01 12:41:59 UTC 
Created attachment 1446677 [details]
/var/log/anaconda/syslog
Comment 13 Chris Williams 2020-11-11 21:42:44 UTC 
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Note You need to log in before you can comment on or make changes to this bug.