| 2021-11-04 10:22:06 |
Lukas Märdian |
bug |
|
|
added bug |
| 2021-11-04 10:22:19 |
Lukas Märdian |
nominated for series |
|
Ubuntu Jammy |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
bug task added |
|
netplan.io (Ubuntu Jammy) |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
bug task added |
|
netplan.io (Ubuntu Hirsute) |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
nominated for series |
|
Ubuntu Impish |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
bug task added |
|
netplan.io (Ubuntu Impish) |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
nominated for series |
|
Ubuntu Focal |
|
| 2021-11-04 10:22:19 |
Lukas Märdian |
bug task added |
|
netplan.io (Ubuntu Focal) |
|
| 2021-11-05 15:05:55 |
Lukas Märdian |
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. |
[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 TBD:
* Impish: amd64, arm64, armhf, ppc64el, s390x
* Hirsute: amd64, arm64, armhf, ppc64el, s390x
* Focal: amd64, arm64, armhf, ppc64el, s390x
[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. |
|
| 2021-11-05 21:58:42 |
Steve Langasek |
netplan.io (Ubuntu Jammy): status |
New |
Fix Committed |
|
| 2021-11-05 22:17:38 |
Steve Langasek |
netplan.io (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-11-05 22:17:42 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-11-05 22:17:44 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2021-11-05 22:17:47 |
Steve Langasek |
tags |
|
verification-needed verification-needed-focal |
|
| 2021-11-05 22:20:26 |
Steve Langasek |
netplan.io (Ubuntu Impish): status |
New |
Fix Committed |
|
| 2021-11-05 22:20:32 |
Steve Langasek |
tags |
verification-needed verification-needed-focal |
verification-needed verification-needed-focal verification-needed-impish |
|
| 2021-11-05 22:30:53 |
Steve Langasek |
netplan.io (Ubuntu Hirsute): status |
New |
Fix Committed |
|
| 2021-11-05 22:31:00 |
Steve Langasek |
tags |
verification-needed verification-needed-focal verification-needed-impish |
verification-needed verification-needed-focal verification-needed-hirsute verification-needed-impish |
|
| 2021-11-10 14:35:40 |
Lukas Märdian |
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 TBD:
* Impish: amd64, arm64, armhf, ppc64el, s390x
* Hirsute: amd64, arm64, armhf, ppc64el, s390x
* Focal: amd64, arm64, armhf, ppc64el, s390x
[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. |
[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. |
|
| 2021-11-10 14:48:10 |
Lukas Märdian |
tags |
verification-needed verification-needed-focal verification-needed-hirsute verification-needed-impish |
verification-done-impish verification-needed verification-needed-focal verification-needed-hirsute |
|
| 2021-11-10 14:57:40 |
Lukas Märdian |
tags |
verification-done-impish verification-needed verification-needed-focal verification-needed-hirsute |
verification-done-hirsute verification-done-impish verification-needed verification-needed-focal |
|
| 2021-11-10 15:20:14 |
Lukas Märdian |
tags |
verification-done-hirsute verification-done-impish verification-needed verification-needed-focal |
verification-done-focal verification-done-hirsute verification-done-impish verification-needed |
|
| 2021-11-17 00:22:59 |
Launchpad Janitor |
netplan.io (Ubuntu Impish): status |
Fix Committed |
Fix Released |
|
| 2021-11-17 00:23:17 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-11-17 00:24:04 |
Launchpad Janitor |
netplan.io (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-11-17 00:25:22 |
Launchpad Janitor |
netplan.io (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-11-24 17:20:33 |
Launchpad Janitor |
netplan.io (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
