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:

Line from kickstart:

network --device=bond0 --bondslaves=en0,en1 --bondopts=mode=active-backup,miimon=100 --noipv6 --bootproto static --ip=192.168.0.22 --netmask=255.255.255.000 --gateway=192.168.0.254 --nameserver=192.168.0.255 --hostname test.example.com
network --device=en0 --activate
network --device=en1 --activate

after the build completes, bond0 is up and NIC ens224 is active. the other slave NIC is _ens192. When I failover to _ens192 using `ifenslave -c bond0 _ens192` the command succeeds but then bond0 is no longer reachable (can't even ping the gateway). 


Version-Release number of selected component (if applicable):


How reproducible:
Very

Steps to Reproduce:
1. Create a kickstart with the bonding options in  https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-commands
2. Kickstart system
3.

Actual results:

bond0 is up and NIC ens224 is active. the other slave NIC is _ens192. When I failover to _ens192 using `ifenslave -c bond0 _ens192` the command succeeds but then bond0 is no longer reachable (can't even ping the gateway). 


Expected results:

For second nic to function properly.

Additional info: