Bug 1756923

Summary: RHVH-4.4.0 Bond failed, there is no slave NIC under the Bond
Product: Red Hat Enterprise Virtualization Manager Reporter: peyu
Component: redhat-virtualization-hostAssignee: Yuval Turgeman <yturgema>
Status: CLOSED ERRATA QA Contact: peyu
Severity: high Docs Contact:
Priority: high    
Version: 4.4.0CC: cshao, lsvaty, mavital, mburman, mtessun, nlevy, peyu, qiyuan, sbonazzo, weiwang, yaniwang, yturgema
Target Milestone: ovirt-4.4.0Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 16:22:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1701464    
Attachments:
Description Flags
Bond without NICs none

Description peyu 2019-09-30 08:33:24 UTC
Created attachment 1621013 [details]
Bond without NICs

Description of problem:
Create Bond through cockpit, after rebooting, there is no slave NIC under the Bond.

Version-Release number of selected component (if applicable):
Test version:
RHVH-4.4-20190926.3-RHVH-x86_64-dvd1.iso

How reproducible:
100%

Steps to Reproduce:
1. Install RHVH-4.4-20190926.3-RHVH-x86_64-dvd1.iso
2. Finish installation and reboot
3. Login to cockpit
4. In networking page, click "Add Bond"
5. Input Bond name, mode and other infos
6. Configure Bond to ipv4 and ipv6 with DHCP mode
7. Reboot RHVH, check Bond via cockpit and shell

Actual results:
1. In step 6, Bond can get IP. But after rebooting, in step7,the Bond status is "Configuring IP" and there is no slave NICs under the Bond.

Expected results:
1. In step 7, Bond can be enabled and can get correct IPv4 and IPv6 address.

Additional info:

Comment 18 peyu 2019-12-04 05:51:45 UTC
This issue did not happen in redhat-virtualization-host-4.4.0-20191201.0.el8_1

Test steps:
1. Install redhat-virtualization-host-4.4.0-20191201.0.el8_1
2. Finish installation and reboot
3. Login to cockpit
4. In networking page, click "Add Bond"
5. Input Bond name, mode and other infos
6. Configure Bond ipv4 and ipv6 using DHCP mode
7. Reboot RHVH, check Bond via cockpit and shell

Test results:
1. In step 6, Bond can get IPs, after rebooting, the bond configuration can be persisted.

So, when the bug status is ON_QA, I will move it to VERIFIED.

Comment 20 errata-xmlrpc 2020-08-04 16:22:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHV Host (redhat-virtualization-host) 4.4), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:3316