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

Bug 1938671

Summary: [Assisted-4.7][nmstate] Hosts fail connectivity check when using bonded interface
Product: OpenShift Container Platform Reporter: nshidlin <nshidlin>
Component: assisted-installerAssignee: yevgeny shnaidman <yshnaidm>
assisted-installer sub component: discovery-agent QA Contact: Omri Hochman <ohochman>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: akaris, lgamliel, m, trwest, zbitter
Version: 4.7   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: OCP-Metal-v1.0.18.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-28 08:45:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
json payload to generate ISO with bonded interfaces on each host none

Description nshidlin 2021-03-15 07:22:53 UTC
Created attachment 1763320 [details]
json payload to generate ISO with bonded interfaces on each host

Description of problem:
In the case of using nmstate to define bonded interfaces hosts fail connectivity check and remain in insufficient state.

Each host is reachable through a ping to each other host
Each host can resolve MAC address on bond for each host using arping:

arping -c 1 -w 2 -I bond0 192.168.123.31
ARPING 192.168.123.31 from 192.168.123.32 bond0
Unicast reply from 192.168.123.31 [52:54:00:9E:E9:03]  0.893ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)


How reproducible:
Every time

Steps to Reproduce:
1. Generate ISO with attached json payload to configure a bond interface on each host in the cluster
2. Boot nodes into ISO and wait for discovery

Actual results:
Hosts fail connectivity check and remain in insufficient status

Expected results:
Host should pass connectivity check

Additional info:
assisted-service log of failed connectivity check:
time="2021-03-15T06:04:49Z" level=info msg="Received step reply <connectivity-check-5b9aaf17> from cluster <e2a12bdc-3469-479a-9a10-22b4dd2ffc01> host <d46d5007-cb82-48c8-be
6d-18691de92a8a>  exit-code <0> stdout <{\"remote_hosts\":[{\"host_id\":\"a47a4bff-bd77-4603-9b53-400a299bac70\",\"l2_connectivity\":[],\"l3_connectivity\":[]},{\"host_id\":
\"b694414c-ce4e-4f48-96ab-9f72e57a27bf\",\"l2_connectivity\":[],\"l3_connectivity\":[]},{\"host_id\":\"5e9c971f-cc11-4ae8-81e2-ee0d4b7a5e3f\",\"l2_connectivity\":[],\"l3_con
nectivity\":[]},{\"host_id\":\"b390627e-4990-4cc0-a2a0-ece28d3e48f6\",\"l2_connectivity\":[],\"l3_connectivity\":[]}]}> stderr <>" func="github.com/openshift/assisted-servic
e/internal/bminventory.(*bareMetalInventory).PostStepReply" file="/go/src/github.com/openshift/origin/internal/bminventory/inventory.go:2814" cluster_id=e2a12bdc-3469-479a-9
a10-22b4dd2ffc01 go-id=144402 host_id=d46d5007-cb82-48c8-be6d-18691de92a8a pkg=Inventory request_id=5e29cd86-aee1-4942-8185-a10d74af2590

Comment 1 nshidlin 2021-03-21 12:36:59 UTC
Verified on master
Component versions:
Assisted Installer
quay.io/ocpmetal/assisted-installer:9b21fb43cca684ff4de4c8ef9682e1c0f36133c0
Assisted Installer Controller
quay.io/ocpmetal/assisted-installer-controller:9b21fb43cca684ff4de4c8ef9682e1c0f36133c0
Assisted Installer Service
quay.io/ocpmetal/assisted-service:15cd03c7e548767786d9649f986730348b7e7321
Discovery Agent
quay.io/ocpmetal/assisted-installer-agent:d28226138b29a122d2bae5108e81cebf693bb105

Comment 2 Andreas Karis 2021-03-30 09:37:14 UTC
*** Bug 1944559 has been marked as a duplicate of this bug. ***

Comment 3 Andreas Karis 2021-03-30 09:39:34 UTC
Hi,

This question is only half related: in 1944559, the customer directly modified the kernel cmdline to configure bonding. Here, you are using a JSON.

The customer isusing the provided iso to boot up their nodes and during startup they edit the kernel cmd line to apply the LACP config like this:
~~~
bond=bond0:eno1np0,ens1f0np0:mode=802.3ad,lacp_rate=fast,miimon=100,xmit_hash_policy=layer2+3 ip=bond0:dhcp
~~~

I do not see anything in https://cloud.redhat.com/openshift/assisted-installer to inject custom configuration, so how can I actually customize the assisted-installer?

Thanks and sorry for the noise, I know this is a BZ and not a forum, but I hope this way I can reach out to the right people at least :-)

- Andreas

Comment 6 Maksim Makarov 2022-08-14 12:33:28 UTC
Is this still not fixed?