[Bug 1949761] Re: NM backend does not accept "scope: link" routes

[Launchpad Bug Tracker]

This bug was fixed in the package netplan.io - 0.103-0ubuntu7.1

---------------
netplan.io (0.103-0ubuntu7.1) impish; urgency=medium

  [ Nicolas Bock ]
  * d/p/0001-Add-support-for-additional-Link-options-225-LP-17717.patch:
    - Add offload configuration options.
      (LP: #1771740)
  * Add d/p/partial-d4884cfd40e1e33540b274371c3272df6595d22c.patch:
    - Partial application of d4884cfd40e1e33540b274371c3272df6595d22c in order
      preserve ABI compatibility for future updates.

  [ Lukas Märdian ]
  * Add d/p/0010-parse-nm-Handle-missing-gateway-in-keyfile-routes-ke.patch
    (LP: #1949761)
  * Fix regression in 'netplan try' (LP: #1949104)
    + d/p/lp1949104/cli-apply-initialize-self.state-LP-1949104-243.patch
    + d/p/lp1949104/tests-regressions-make-netplan_try-autopkgtest-more-.patch

 -- Lukas Märdian <slyon at ubuntu.com>  Fri, 05 Nov 2021 14:44:08 +0100

** Changed in: netplan.io (Ubuntu Impish)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1949761

Title:
  NM backend does not accept "scope: link" routes

Status in netplan.io package in Ubuntu:
  Fix Committed
Status in netplan.io source package in Focal:
  Fix Released
Status in netplan.io source package in Hirsute:
  Fix Released
Status in netplan.io source package in Impish:
  Fix Released
Status in netplan.io source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The NetworkManager snap (using the libnetplan YAML backend) makes use of the
  "link" routing scope in certain situations, which is represented by an empty or
  unspecified gateway/next_hop field in the keyfile definition (e.g.
  "route3=2.2.2.2/7", "route4=3.3.3.3/6,0.0.0.0,4", "route3=4:5:6:7:8:9:0:1/63,,5)
  We need to make sure netplan is able to read and write such routing information.

  [Test Plan]
  In addition to runing & passing the full set of unit- and integration-tests
  (that contains new tests to check for this regression), as described in
  https://wiki.ubuntu.com/NetplanUpdates we want to run the following commands
  to make sure the 'netplan try' command is working properly:

  $ mkdir -p tmp/etc/netplan
  $ cat tmp/etc/netplan/test.yaml
  network:
    renderer: NetworkManager
    ethernets:
      eth0:
        addresses: [1.2.3.4/24, fe20::3/16]
        routes:
        - to: 2.2.2.2/7
          scope: link
        - to: 3.3.3.3/6
          scope: link
          metric: 4
        - to: 4:5:6:7:8:9:0:1/63
          scope: link
          metric: 5
  $ /usr/lib/netplan/generate -r tmp/
  $ cat tmp/run/NetworkManager/system-connections/netplan-eth0.nmconnection | grep "route.="

  => Make sure it generated the "scope: link" routes with empty/missing
  gateway.

  autopkgtest logs:
  * Impish:
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_amd64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_arm64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_armhf.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_ppc64el.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_s390x.log
  * Hirsute:
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_amd64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_arm64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_armhf.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_ppc64el.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_s390x.log
  * Focal:
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_amd64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_arm64.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_armhf.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_ppc64el.log
  https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_s390x.log

  [Where problems could occur]
  This upload touches netplan's keyfile parser and keyfile generator, if anything
  goes wrong it could impact the NetworkManager snap (using the libnetplan YAML
  backend & keyfile parser) and the netplan generator itself in cases where the
  NetworkManager backend/renderer is used.

  [Other Info]
  The full set of autopkgtest logs will be attached after the upload is accepted
  into -proposed and the tests have been run on the official autopkgtest.u.c
  infrastructure.

  === Original Description ===

  NetworkManager keyfiles allows to specify "scope: link" routes, by
  leaving the gateway/next_hop field unspecified, e.g.:

  route3=2.2.2.2/7
  route4=3.3.3.3/6,0.0.0.0,4

  route3=4:5:6:7:8:9:0:1/63,::,5

  To keep compatibility, netplan needs to be able to accept "scope:
  link" routes for the NM backend and render the keyfile accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1949761/+subscriptions