Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1835105

Summary: [4.3] Unable to add a host to RHV over BOND management interfaces created by IBM cloud
Product: [oVirt] vdsm Reporter: Evgeny Slutsky <eslutsky>
Component: GeneralAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.30.43CC: bugs, dholler, mperina
Target Milestone: ovirt-4.5.0Flags: mperina: ovirt-4.5?
Target Release: 4.50   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-06 09:41:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine events screenshot
none
vdsm logs none

Comment 1 Evgeny Slutsky 2020-05-13 06:31:50 UTC
Created attachment 1687932 [details]
engine events screenshot

Comment 2 Evgeny Slutsky 2020-05-13 06:40:14 UTC
Created attachment 1687936 [details]
vdsm logs

Comment 3 Michael Burman 2020-05-13 06:44:15 UTC
Hi Evegeny

I see you have 2 bonds with IPv4 addresses. 
How do you add the host RHV, over hostname or IPv4 address of bond1? does the hostname resolves to the address of bond1?
Also, how did you created the bond before trying to add to RHV? pls provide the output of ifcfg-bond1

In 4.3 it should contain NM_CONTROLLED=no

Comment 5 Michael Burman 2020-05-13 07:07:26 UTC
How bond1 was created? manually using ifcfg? via cockpit?

Comment 9 Ales Musil 2021-10-06 09:41:59 UTC
Closing as current release, we have switched to NM and nmstate in RHV 4.4. 
Please reopen the bug if it pops up again.

Comment 10 Sandro Bonazzola 2022-04-20 06:30:33 UTC
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.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.