| 2020-01-15 18:52:29 |
Dan Streetman |
bug |
|
|
added bug |
| 2020-01-15 18:55:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-15 18:55:58 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Eoan) |
|
| 2020-01-15 18:55:58 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-01-15 18:55:58 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2020-01-15 18:56:06 |
Dan Streetman |
nominated for series |
|
Ubuntu Disco |
|
| 2020-01-15 18:56:06 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Disco) |
|
| 2020-01-15 18:56:11 |
Dan Streetman |
systemd (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2020-01-15 18:56:14 |
Dan Streetman |
systemd (Ubuntu Eoan): status |
New |
In Progress |
|
| 2020-01-15 18:56:15 |
Dan Streetman |
systemd (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-01-15 18:56:17 |
Dan Streetman |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2020-01-15 18:56:19 |
Dan Streetman |
systemd (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-01-15 18:56:22 |
Dan Streetman |
systemd (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-01-15 18:56:24 |
Dan Streetman |
systemd (Ubuntu Eoan): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-01-15 18:56:25 |
Dan Streetman |
systemd (Ubuntu Bionic): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-01-15 19:41:34 |
Dan Streetman |
description |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
TBD
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info] |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info] |
|
| 2020-01-15 19:42:20 |
Dan Streetman |
description |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info] |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic, this is a regression introduced by bug 1850704. |
|
| 2020-01-15 19:43:49 |
Dan Streetman |
description |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic, this is a regression introduced by bug 1850704. |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic, this is a regression introduced by bug 1850704. However, manual disabling of ipv6 is very unusual, so this bug is unlikely to have an impact to many systems. |
|
| 2020-02-03 21:55:12 |
Steve Langasek |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-03 21:55:16 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-02-03 21:55:20 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2020-02-03 21:55:24 |
Steve Langasek |
tags |
|
verification-needed verification-needed-bionic |
|
| 2020-02-06 15:23:18 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Fix Committed |
In Progress |
|
| 2020-02-06 21:48:11 |
Steve Langasek |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-16 14:20:32 |
Dan Streetman |
description |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic, this is a regression introduced by bug 1850704. However, manual disabling of ipv6 is very unusual, so this bug is unlikely to have an impact to many systems. |
[impact]
if the 'disable_ipv6' procfs setting is disabled, and networkd is configured with ipv6 networking, networkd will not enable ipv6 via the procfs setting unless the interface mtu is also set to a custom value, that doesn't match the current interface mtu.
[test case]
create networkd config similar to:
[Match]
MACAddress=52:54:00:0c:09:77
Name=ens3
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=2001:db8::100/64
manually disable ipv6 for the interface:
ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
the interface should not contain any ipv6 addresses:
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not:
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$
Note that with the mtu set, it will successfully re-enable ipv6; modify the networkd config to set the mtu by adding this:
[Link]
MTUBytes=1400
(be sure to set the MTU config to something other than its current mtu)
verify ipv6 is still disabled and has no addresses, then restart and check again:
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
1
ubuntu@lp1859862-b:~$ ip -6 a show ens3
ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd
ubuntu@lp1859862-b:~$ cat /proc/sys/net/ipv6/conf/ens3/disable_ipv6
0
ubuntu@lp1859862-b:~$ ip -6 a show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 state UP qlen 1000
inet6 2001:db8::100/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe0c:977/64 scope link
valid_lft forever preferred_lft forever
That should be the behavior even if MTUBytes is not set.
[regression potential]
as this adjusts when the procfs 'disable_ipv6' setting is changed, the regression potential could cause failure to properly set/create ipv6 addresses, or to leave ipv6 disabled entirely.
[scope]
This is needed in Bionic and Eoan.
the commit to fix this is 482efedc081b0c4bf2e77a3dee6b979d9c9a5765 which is included starting in v243, so it is included already in Focal.
Ignoring Disco, as it is EOL next week.
This problem was introduced by commit 44b598a1c9d11c23420a5ef45ff11bcb0ed195eb, which was included starting in v239, but also backported to Bionic in bug 1850704.
[other info]
for Eoan, this bug has always existed since release, but for Bionic, this is a regression introduced by bug 1850704. However, manual disabling of ipv6 is very unusual, so this bug is unlikely to have an impact to many systems. |
|
| 2020-02-16 14:31:01 |
Dan Streetman |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2020-02-17 09:58:04 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-02-17 10:07:54 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-04-27 15:50:55 |
Łukasz Zemczak |
systemd (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-04-27 15:50:57 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-04-27 15:51:01 |
Łukasz Zemczak |
tags |
verification-done verification-done-bionic |
verification-done-bionic verification-needed verification-needed-eoan |
|
| 2020-05-07 09:42:53 |
Dan Streetman |
tags |
verification-done-bionic verification-needed verification-needed-eoan |
verification-done verification-done-bionic verification-done-eoan |
|
| 2020-05-11 15:06:36 |
Launchpad Janitor |
systemd (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
