Created attachment 779704 [details] error in creating bond +++ This bug was initially created as a clone of Bug #988341 +++ Description of problem: It should not create bond in Network page when report an error while configuration process failed. And it only create bond button but no option in Available System NICs. So it should not create bond button and let the NIC display. Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.0-3.999.999.20130716190656git4e57356.2850.fc18.src.rpm ovirt-node-3.0.0-3.999.20130716190656git4e57356.fc18.noarch How reproducible: 100% Steps to Reproduce: 1. Clear install ovirt-node. 2. Configure network using eth2 3. Create bond0. Select eth0, eth2 and apply. report error as follows: Transaction:Network Interface Configuration Checking pre-conditions.... (1/7) Writing bond master configuration (2/7) Writing bond slaves configuration An error occurred while applying the changes: Bond slave can not be used as primary device 4. Check in Network page. 5. Check in status page. 6. Check ping. Actual results: In step4, the eth2 disappeared and it have added 'remove bond1(eth2,eth0)' button. In step5, the networking status change to Unknown with no ip address. In step6, it can ping outside. Expected results: In step4, it should roll back to the settings before. Additional info:
This issue can be reproduced on the fellow bulid: rhev-hypervisor6-6.5-20130725.0.el6 ovirt-node-3.0.0-6.1.el6.noarch So need to clone it from ovirt-node upstream to downstream to track this issue.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Re-targeting for 3.6
This functionality will move to cockpit, where this bug does not apply anymore.