Bug 1835105 - [4.3] Unable to add a host to RHV over BOND management interfaces created by IBM cloud
Summary: [4.3] Unable to add a host to RHV over BOND management interfaces created by ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.30.43
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.0
: 4.50
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-13 06:19 UTC by Evgeny Slutsky
Modified: 2022-04-20 06:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-06 09:41:59 UTC
oVirt Team: Network
Embargoed:
mperina: ovirt-4.5?


Attachments (Terms of Use)
engine events screenshot (165.77 KB, image/png)
2020-05-13 06:31 UTC, Evgeny Slutsky
no flags Details
vdsm logs (14.39 KB, application/gzip)
2020-05-13 06:40 UTC, Evgeny Slutsky
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-37690 0 None None None 2021-10-06 07:14:32 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.