Bug 689702

Summary: Unable to re-provision a system with a bonded interface from RHN Satellite v5.4
Product: Red Hat Satellite 5 Reporter: Paresh Mutha <pmutha>
Component: ProvisioningAssignee: Tomas Lestach <tlestach>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: bugzilla-redhat, cperry, juergen.schilp, mdavis, mosvald, stanislav.polasek, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 589318 Environment:
Last Closed: 2011-03-23 09:38:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 677498    

Comment 1 Paresh Mutha 2011-03-22 08:37:52 UTC
Public Summary :

Description of problem:
If a system is currently operating with a bonded interface (ie bond0 with eth0 and eth1), it does not retain the original bonding configuration after the system is re-provisioned.

Version-Release number of selected component (if applicable):
Red Hat Network Satellite v5.4

How reproducible:
Always

Steps to Reproduce:
1. Configure bonding on a client system (on eth0 and eth1)
2. Register it on Satellite server with provisioning entitlement
3. Go to Provisioning tab
4. Select KS profile and then under Advanced Configuration - select "Use DHCP from interface (bond0) "
5. Re-provision the system

Actual results:
When system is rebooted the installation ask for the ethernet card to select then it complete the installation successfully. If we check the ifconfig command o/p after installation then only eth0 is replaced by bond0 but the eth1 get IP from DHCP. 

Expected results:
Bonding should be configured as it was before provisioning the system.

Comment 2 Paresh Mutha 2011-03-23 09:38:38 UTC

*** This bug has been marked as a duplicate of bug 589318 ***