Bug 1935710 - Nmstate fails configuring networking on unrelated devices when they are unmanaged
Summary: Nmstate fails configuring networking on unrelated devices when they are unman...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Fernando F. Mancera
QA Contact: Mingyu Shi
Depends On:
TreeView+ depends on / blocked
Reported: 2021-03-05 12:40 UTC by Quique Llorente
Modified: 2021-11-09 20:18 UTC (History)
6 users (show)

Fixed In Version: nmstate-1.0.2-6.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-11-09 17:43:40 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)
NodeNetworkConfigurationPolicy to apply (481 bytes, text/plain)
2021-03-05 12:40 UTC, Quique Llorente
no flags Details
Node Network State (6.35 KB, text/plain)
2021-03-05 12:41 UTC, Quique Llorente
no flags Details
Node Network State raw (11.71 KB, text/plain)
2021-03-05 12:41 UTC, Quique Llorente
no flags Details
Error log (46.58 KB, text/plain)
2021-03-05 12:42 UTC, Quique Llorente
no flags Details
Reproducer (388 bytes, application/x-shellscript)
2021-03-15 13:27 UTC, Ales Musil
no flags Details
verified.log (91.55 KB, text/plain)
2021-04-06 09:56 UTC, Mingyu Shi
no flags Details

System ID Private Priority Status Summary Last Updated
Github nmstate/nmstate/commit/ccdcd8f86544a6364109a0c0142d05a5afacf64e 0 None None None 2021-03-23 13:04:04 UTC
Red Hat Product Errata RHBA-2021:4157 0 None None None 2021-11-09 17:44:01 UTC

Description Quique Llorente 2021-03-05 12:40:43 UTC
Created attachment 1760891 [details]
NodeNetworkConfigurationPolicy to apply

Created attachment 1760891 [details]
NodeNetworkConfigurationPolicy to apply

Description of problem:
When doing some network configuration [1] and you have some devices marked as unmanaged at NetworkManager nmstate fails on those devices even if they are not part of the devices being configured.

Version-Release number of selected component (if applicable):
nmstate 1.0.2
NetworkManager 1.30

How reproducible: Always

Steps to Reproduce:
1.git clone https://github.com/qinqon/kubernetes-nmstate
2.cd kubernetes-nmstate
3.git checkout pin-network-manager-at-node
4.make NMSTATE_PIN=future cluster-up cluster-sync
5.cat nncp.yaml | ./cluster/kubectl.sh exec -it -n nmstate $(./cluster/kubectl.sh get pod -n nmstate -l component=kubernetes-nmstate-handler |grep nmstate |awk '{print $1}' |head -n 1) -- nmstatectl set

Actual results:
libnmstate.error.NmstateLibnmError: Activate profile uuid:a55c98f8-fadc-46cb-b79a-5864ce2bf4d5 iface:cali1a2cfcdd5b6 type: veth failed: error=nm-manager-error-quark: Connection 'cali1a2cfcdd5b6' is not available on device cali1a2cfcdd5b6 because device is strictly unmanaged (2)
command terminated with exit code 1

Expected results:
To succeed

Additional info:

Calico device are marked at unmanaged at NetworkManager configuration
[vagrant@node01 ~]$ cat /etc/NetworkManager/conf.d/001-calico.conf 

To access ssh into the node you can do ./cluster/ssh.sh node01

Comment 1 Quique Llorente 2021-03-05 12:41:22 UTC
Created attachment 1760892 [details]
Node Network State

Comment 2 Quique Llorente 2021-03-05 12:41:54 UTC
Created attachment 1760893 [details]
Node Network State raw

Comment 3 Quique Llorente 2021-03-05 12:42:25 UTC
Created attachment 1760894 [details]
Error log

Comment 4 Ales Musil 2021-03-15 13:27:14 UTC
Created attachment 1763385 [details]

I have created reproducer script. One thing to note is that this works 100% in 
container. The key to this is that the container has DNS that is not managed by NM
upon creation.

Comment 9 Mingyu Shi 2021-04-06 09:56:19 UTC
Created attachment 1769525 [details]

Verified with versions:

Comment 10 Quique Llorente 2021-06-01 14:36:58 UTC
I have also test it and it's working fine now.

Comment 12 errata-xmlrpc 2021-11-09 17:43:40 UTC
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 (nmstate 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.


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