Created attachment 1584634 [details] Log files Description of problem: After deleting bond in cockpit, the slave NICs are still inactive status. According to test case, they should be up and get the DHCP IP. Version-Release number of selected component (if applicable): RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso cockpit-system-195-1.el7.noarch cockpit-195-1.el7.x86_64 cockpit-bridge-195-1.el7.x86_64 cockpit-ws-195-1.el7.x86_64 cockpit-machines-ovirt-195-1.el7.noarch cockpit-dashboard-195-1.el7.x86_64 cockpit-storaged-195-1.el7.noarch cockpit-ovirt-dashboard-0.13.2-2.el7ev.noarch NetworkManager-1.18.0-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Clean install RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso 2. Login to "http://localhost:9090" 3. Create bond with two dhcp NICs in Cockpit Network 4. Delete the bond 5. Check the slave NICs Actual results: The slave NICs are still inactive status after deleting bond successfully in cockpit. Expected results: The slave NICs should be up status and get the DHCP IP successfully. Additional info:
blocked on cockpit fix for this. we'll need to rebase once fix is available.
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5.
Waiting on RHEL/CentOS Linux 8.2
This should be fixed in cockpit-211.3-1 included in RHEL 8.2 which will land soon in CentOS 8.2.
cockpit-217 has been added to https://copr.fedorainfracloud.org/coprs/sbonazzo/EL8_collection/builds/ for ovirt 4.4.0 consumption
Test Version RHVH-4.4-20200507.1-RHVH-x86_64-dvd1.iso cockpit-211.3-1.el8.x86_64 cockpit-ovirt-dashboard-0.14.6-1.el8ev.noarch cockpit-system-211.3-1.el8.noarch cockpit-ws-211.3-1.el8.x86_64 cockpit-dashboard-211.3-1.el8.noarch subscription-manager-cockpit-1.26.17-1.el8_2.noarch cockpit-storaged-211.3-1.el8.noarch cockpit-bridge-211.3-1.el8.x86_64 Test Result: Bug is fixed, so move status to "VERIFIED"
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.