December 2019 - nmstate-devel - Fedora mailing-lists

Checkpoint logic error for integration test tear-up phase
by Till Maas 15 Feb '20

15 Feb '20

Hi, while looking at Nmstate logs after failures I noticed that Nmstate uses checkpoints in the tear-up phase of integration tests. Therefore, if something fails inside the mainloopo in the tear-up phase, all tear-up progress is reverted instead of keeping at least the removed bits removed. Am I missing something? My idea for the easiest/cleanest solution would be to just issue "nmcli c d $interface; nmclid d $interface (if it is not eth1/eth2)" and ignoring the returncode for all interfaces that are touched in a test as the tear-up code. Since Nmstate also stores routes and DNS information in the respective profiles, this should properly clean it up with the better working nmcli code. What do you think? Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

2 2

Nmstate 0.2 next version
by Edward Haas 06 Jan '20

06 Jan '20

Hi Gris, Fernando, All Tyll raised a good point that nmstate-0.1.2 had newer content than nmstate-0.2.0 and therefore it makes sense to release a new 0.2 version. With that said, we could delay the release if we have some content we still want in from the pending PR/s. Please feedback with your thoughts. Thanks, Edy.

4 3

[ANNOUNCE] nmstate 0.1.2 release
by Fernando Fernandez Mancera 16 Dec '19

16 Dec '19

Hi! The Nmstate project proudly presents: nmstate 0.1.2 This release contains bug fixes and some break changes. => Break Changes * Deprecation in libnmstate.schema: * 'LinuxBridge.GROUP_FORWARD_MASK' -> 'LinuxBridge.Options.GROUP_FORWARD_MASK' * 'LinuxBridge.MAC_AGEING_TIME' -> 'LinuxBridge.Options.MAC_AGEING_TIME', * 'LinuxBridge.MULTICAST_SNOOPING' -> 'LinuxBridge.Options.MULTICAST_SNOOPING' => Bug Fixes * Skip editing interfaces with unknown type * Fix verification failure when applying route rule to 2+ route tables. Please note that the Fedora and Copr packages are already available. * Fedora 31: https://koji.fedoraproject.org/koji/buildinfo?buildID=1420801 * Copr: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate-0.1/package/nmstate/ Happy networking!

1 0

Nmstate now uses double quotes for string constants
by Till Maas 12 Dec '19

12 Dec '19

Hi, since now, Nmstate now follows the black default and uses double quotes for string constants. If you prefer to code with single ticks, you can still do so and use the black tool to convert them to double quotes by running "black ." in your working copy. Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

1 0

Checking libnm/NM version mismatch
by Till Maas 09 Dec '19

09 Dec '19

Hi, one of the Nmstate ours accidentally used Nmstate on a machine after updating NM without restarting it on CentOS 8. Therefore the system used libnm 1.20 with NM 1.14. This resulted in an error like Connection adding failed: error=nm-connection-error-quark: bridge.vlans: unknown property (7) How can we improve this error message? My initial idea would be to compare the versions of NM and libnm in Nmstate and warn/abort if there is a mismatch: AFAICS we can check the NM version with NMClient.get_version() and the libnm version seems to be available with struct.unpack("xBBB", struct.pack(">I", NM.utils_version())) (not so convenient that the version identifiers are in different encodings, to be honest). How about we add a warning/an error to Nmstate in case the versions mismatch? Do you prefer a warning or an error? Do you have other suggestions? Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, https://www.redhat.com/de, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael O'Neill, Tom Savage, Eric Shander

4 6

Problem with MAC address pattern
by Fernando Fernandez Mancera 09 Dec '19

09 Dec '19

Hello, Recently I've been trying nmstate in a server with an infiniband interface and I've found the following error. [root@zeus08 nmstate]# nmstatectl show Traceback (most recent call last): File "/usr/local/bin/nmstatectl", line 11, in <module> load_entry_point('nmstate==0.2.1', 'console_scripts', 'nmstatectl')() File "/usr/local/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 59, in main return args.func(args) File "/usr/local/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 203, in show state = _filter_state(libnmstate.show(), args.only) File "/usr/local/lib/python3.6/site-packages/libnmstate/netinfo.py", line 71, in show validator.validate(report) File "/usr/local/lib/python3.6/site-packages/libnmstate/validator.py", line 56, in validate js.validate(data, validation_schema) File "/usr/local/lib/python3.6/site-packages/jsonschema/validators.py", line 934, in validate raise error jsonschema.exceptions.ValidationError: '80:00:02:08:FE:80:00:00:00:00:00:00:F4:52:14:03:00:61:AA:91' does not match '^([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}$' Failed validating 'pattern' in schema['properties']['interfaces']['items']['allOf'][0]['properties']['mac-address']: {'pattern': '^([a-fA-F0-9]{2}:){5}[a-fA-F0-9]{2}$', 'type': 'string'} On instance['interfaces'][10]['mac-address']: '80:00:02:08:FE:80:00:00:00:00:00:00:F4:52:14:03:00:61:AA:91' It seems that MAC pattern is not working for this MAC address. Here is the "ip" output for this interface. 8: ib0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 4092 qdisc fq_codel state DOWN group default qlen 256 link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:f4:52:14:03:00:61:aa:91 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff Should I open a card for this? What do you think? Thanks, Fernando.

2 1

Remove branches "stable" and "stable_v0.0.8"
by Till Maas 09 Dec '19

09 Dec '19

Hi, as discussed I just removed the branches "stable" and "stable_v0.0.8". Please remember to use "git fetch --prune" in case you have any working copies from the official GitHub repository to remove the branches locally as well (if you do not need them). Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

1 0

Branches `stable` and `stable_v0.0.8` on GitHub - ok to remove?
by Till Maas 08 Dec '19

08 Dec '19

Hi, there are still the branches `stable` and `stable_v.0.0.8` on GitHub. As far as I know, we do not use them anymore. Is it ok to remove them? Edy, Gris, I will wait for your explicit approval before doing this. Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

3 2

[ANNOUNCE] nmstate 0.2.0 release
by Fernando Fernandez Mancera 04 Dec '19

04 Dec '19

Hi! The Nmstate project proudly presents: nmstate 0.2.0 This release contains bug fixes. => Bug Fixes * Skip editing interfaces with unknown type Please note that the Fedora and Copr packages are already available. * Fedora 32: https://koji.fedoraproject.org/koji/buildinfo?buildID=1419259 * Copr: https://copr.fedorainfracloud.org/coprs/nmstate/nmstate/packages/ Happy networking!

1 0

ANNOUNCEMENT: Copr Repositories change
by Till Maas 04 Dec '19

04 Dec '19

Hi, these are now the official Copr repositories: nmstate -> tagged releases from master (uses Fedora Rawhide dist-git) nmstate-0.1 -> tagged releases from nmstate-0.1 (uses Fedora 31 dist-git) nmstate-git -> automated rebuild from master git branch nmstate-0.1-git -> automated rebuild from nmstate-0.1 git branch In case you are using nmstate-fedora-git, please change it to nmstate-git. nmstate-fedora-git will be removed soon. The update for the README needs a review: https://github.com/nmstate/nmstate/pull/628 Also, the homepage needs an update. But an older update is still stuck in review. Please take a look. Kind regards Till -- Till Maas He/His/Him Ansible RHEL Networking System Role Maintainer Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage

3 5

2025

2024

2023

2022

2021

2020

2019

nmstate-devel December 2019