Bug 2077950
| Summary: | NetworkManager manages devices that it shouldn't | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jaime Caamaño Ruiz <jcaamano> | ||||
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Matej Berezny <mberezny> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.6 | CC: | bgalvani, lrintel, mberezny, rkhan, sfaye, sukulkar, till, vbenes, wenliang | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | NetworkManager-1.39.11-1.el8 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-11-08 10:10:31 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
Jaime Caamaño Ruiz
2022-04-22 16:27:19 UTC
> patch-br-int-to-br-ex_ci-ln-vxc1wlb-72292-b2d6j-worker-a-r4gnj is managed when it shouldn't as per the configuration above.
I see, that's a bug.
Note that NM considers the device as "external" and so even it is marked as "activated", NM doesn't actually touch it:
<info> [1650644081.2483] device (patch-br-int-to-br-ex_ci-ln-vxc1wlb-72292-b2d6j-worker-a-r4gnj): state change: unmanaged -> activated (reason 'connection-assumed', sys-iface-state: 'external')
In other words, apart from the wrong state displayed ("activated" instead of "unmanaged"), NM is not actively managing the interface. Anyway, the wrong state is a bug that must be fixed.
To reproduce, I did: cat <<'EOF' > /etc/NetworkManager/conf.d/01-ovs-int0-unmanaged.conf [device-unmanaged] match-device=interface-name:ovs-int0 managed=no EOF systemctl restart NetworkManager ovs-vsctl add-br ovs-br0 ovs-vsctl add-port ovs-br0 ovs-int0 -- set interface ovs-int0 type=patch -- set interface ovs-int0 options:peer=ovs-br0 and saw in logs: <info> [1658131864.0397] ovs: ovs interface "ovs-int0" ((null)) failed: No usable peer 'ovs-br0' exists in 'system' datapath. <info> [1658131864.0398] device (ovs-int0): state change: unmanaged -> activated (reason 'connection-assumed', sys-iface-state: 'external') Note the ovs-interface transitioning from "unmanaged" to "activated". There are also some assertion failures a bit later: <info> [1658131864.0404] device (ovs-int0): Activation: successful, device activated. _connection_get_setting_by_meta_type_check: assertion 'NM_IS_CONNECTION(connection)' failed _connection_get_setting_by_meta_type_check: assertion 'NM_IS_CONNECTION(connection)' failed _connection_get_setting_by_meta_type_check: assertion 'NM_IS_CONNECTION(connection)' failed With the patch applied, the device stays in state unmanaged and the assertions failures are gone. 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 (NetworkManager bug fix and enhancement update), 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/RHBA-2022:7680 |