Bug 2214881

Summary: NetworkManager has an assertion when OVS adds a device during a cluster update so the node is inaccessible
Product: Red Hat Enterprise Linux 8 Reporter: Jonathan Maxwell <jmaxwell>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: NEW --- QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.4CC: bgalvani, fpokryvk, lrintel, rkhan, sfaye, sukulkar, till
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2218443 (view as bug list) Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 2218443    

Comment 3 Beniamino Galvani 2023-07-04 07:28:43 UTC
Hi,

I tried to reproduce the problem but I couldn't find the conditions to trigger it.

Would it be possible to get a trace log? To capture it, set 'level' to TRACE in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart the NetworkManager service, reproduce and then attach the output of `journalctl -b`. Thanks

> Is this related to https://bugzilla.redhat.com/show_bug.cgi?id=2092323?

No, that one is in nmcli, this is in the daemon.

Comment 4 Jonathan Maxwell 2023-07-04 23:18:19 UTC
(In reply to Beniamino Galvani from comment #3)
> Hi,
> 
> I tried to reproduce the problem but I couldn't find the conditions to
> trigger it.
> 
> Would it be possible to get a trace log? To capture it, set 'level' to TRACE
> in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart
> the NetworkManager service, reproduce and then attach the output of
> `journalctl -b`. Thanks
> 

Howdy,

I have asked the customer and will upload when they provide `journalctl -b`.

Leaving needinfo for me.

Regards

Jon