Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionQuique 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
[keyfile]
unmanaged-devices=interface-name:cali*;interface-name:tunl*
To access ssh into the node you can do ./cluster/ssh.sh node01
Created attachment 1763385[details]
Reproducer
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.
Created attachment 1769525[details]
verified.log
Verified with versions:
nmstate-1.0.2-5.el8.noarch
nispor-1.0.1-4.el8.x86_64
NetworkManager-1.30.0-7.el8.x86_64
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.
https://access.redhat.com/errata/RHBA-2021:4157