| 2019-03-04 14:53:11 |
Abam |
bug |
|
|
added bug |
| 2019-04-08 10:02:18 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2019-04-08 10:06:40 |
Chiang Fong Lee |
bug watch added |
|
https://github.com/systemd/systemd/issues/9833 |
|
| 2019-04-19 15:35:30 |
Upen |
bug |
|
|
added subscriber Upen |
| 2019-06-04 18:36:43 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-06-05 12:28:46 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-06-05 12:28:46 |
Heitor Alves de Siqueira |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2019-06-05 12:28:46 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-06-05 12:28:46 |
Heitor Alves de Siqueira |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2019-06-05 12:28:54 |
Heitor Alves de Siqueira |
systemd (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-06-05 12:29:06 |
Heitor Alves de Siqueira |
systemd (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2019-06-05 12:29:29 |
Heitor Alves de Siqueira |
systemd (Ubuntu Bionic): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2019-06-05 12:29:31 |
Heitor Alves de Siqueira |
systemd (Ubuntu Xenial): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2019-06-05 12:29:34 |
Heitor Alves de Siqueira |
systemd (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-06-05 12:29:35 |
Heitor Alves de Siqueira |
systemd (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2019-06-05 12:29:47 |
Heitor Alves de Siqueira |
bug |
|
|
added subscriber Heitor Alves de Siqueira |
| 2019-06-05 13:47:52 |
Heitor Alves de Siqueira |
description |
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-05 13:47:56 |
Heitor Alves de Siqueira |
systemd (Ubuntu Xenial): status |
New |
Invalid |
|
| 2019-06-05 13:47:58 |
Heitor Alves de Siqueira |
systemd (Ubuntu Xenial): importance |
Medium |
Undecided |
|
| 2019-06-05 13:47:59 |
Heitor Alves de Siqueira |
systemd (Ubuntu Xenial): assignee |
Heitor Alves de Siqueira (halves) |
|
|
| 2019-06-05 13:48:07 |
Heitor Alves de Siqueira |
systemd (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2019-06-05 13:50:29 |
Heitor Alves de Siqueira |
attachment added |
|
lp1818527-bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527/+attachment/5268921/+files/lp1818527-bionic.debdiff |
|
| 2019-06-05 13:50:41 |
Heitor Alves de Siqueira |
tags |
|
sts sts-sponsor |
|
| 2019-06-05 13:50:56 |
Heitor Alves de Siqueira |
bug |
|
|
added subscriber STS Sponsors |
| 2019-06-10 13:06:22 |
Dan Streetman |
tags |
sts sts-sponsor |
sts sts-sponsor sts-sponsor-ddstreet |
|
| 2019-06-10 13:09:10 |
Dan Streetman |
tags |
sts sts-sponsor sts-sponsor-ddstreet |
ddstreet-next sts sts-sponsor sts-sponsor-ddstreet |
|
| 2019-06-10 19:03:34 |
Dan Streetman |
tags |
ddstreet-next sts sts-sponsor sts-sponsor-ddstreet |
ddstreet-next sts sts-sponsor sts-sponsor-ddstreet systemd |
|
| 2019-06-11 18:28:08 |
Eric Desrochers |
description |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd with Cosmic/Disoo/Eoan and late (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan inside a container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-11 18:29:24 |
Eric Desrochers |
description |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd with Cosmic/Disoo/Eoan and late (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan inside a container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-11 18:30:19 |
Eric Desrochers |
description |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd container with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-11 18:49:44 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2019-06-11 18:49:48 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2019-06-11 19:03:57 |
Dan Streetman |
tags |
ddstreet-next sts sts-sponsor sts-sponsor-ddstreet systemd |
sts sts-sponsor systemd |
|
| 2019-06-11 20:19:50 |
Eric Desrochers |
description |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd container with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
....
;; QUESTION SECTION:
;github.com. IN CNAME
;; Query time: 47 msec
.....
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
While in reality, if no non-existent CNAME result query has been made first:
$ systemd-resolve --flush-caches
$ dig github.com | grep "IN" | grep "A"
....
; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 59 IN A 192.30.253.112
;; Query time: 51 msec
....
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd container with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-11 20:20:21 |
Eric Desrochers |
description |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
....
;; QUESTION SECTION:
;github.com. IN CNAME
;; Query time: 47 msec
.....
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
While in reality, if no non-existent CNAME result query has been made first:
$ systemd-resolve --flush-caches
$ dig github.com | grep "IN" | grep "A"
....
; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 59 IN A 192.30.253.112
;; Query time: 51 msec
....
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd container with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific domain, further attempts at resolving A records for that same domain fail. This has been fixed upstream in v240.
Upstream commit: https://github.com/systemd/systemd/commit/3740146a4cbd
$ git describe --contains 3740146a4cbd
v240~839
$ rmadison systemd --arch amd64
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.21 | xenial-updates | source, ...
systemd | 237-3ubuntu10 | bionic | source, ...
systemd | 237-3ubuntu10.19 | bionic-security | source, ...
systemd | 237-3ubuntu10.21 | bionic-updates | source, ...
systemd | 237-3ubuntu10.22 | bionic-proposed | source, ...
systemd | 239-7ubuntu10 | cosmic | source, ...
systemd | 239-7ubuntu10.12 | cosmic-security | source, ...
systemd | 239-7ubuntu10.13 | cosmic-updates | source, ...
systemd | 239-7ubuntu10.14 | cosmic-proposed | source, ...
systemd | 240-6ubuntu5 | disco | source, ...
systemd | 240-6ubuntu5.1 | disco-proposed | source, ...
systemd | 240-6ubuntu9 | eoan | source, ...
Despite the package versions above, only Bionic is affected. Cosmic already includes a backported fix, and Xenial doesn't seem affected due to resolvconf handling DNS resolution.
[Test Case]
Flush resolved's caches and try resolving a non-existent CNAME record. Further resolution attempts for the corresponding A record will fail:
#1
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
....
;; QUESTION SECTION:
;github.com. IN CNAME
;; Query time: 47 msec
.....
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
While in reality, if no non-existent CNAME result query has been made first:
$ systemd-resolve --flush-caches
$ dig github.com
....
; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 59 IN A 192.30.253.112
;; Query time: 51 msec
....
#2
On a Bionic host:
$ systemd-resolve --flush-caches
$ dig github.com CNAME
$ dig github.com A
Build a lxd container with Cosmic/Disco/Eoan (systemd-240):
$ lxc launch ubuntu:cosmic cosmiclxd
$ lxd exec cosmiclxd bash
$ dig github.com A
....
;; QUESTION SECTION:
;github.com. IN A
;; Query time: 0 msec
....
Despite the fact that Cosmic and late has the proper systemd fix, Cosmic/Disco/Eoan container can suffer from the bug too if the host is Bionic (container uses the host as a DNS resolver).
So you may face the problem inside Cosmic/Disco/Eoan container, but it's still the same Bionic systemd bug.
[Regression Potential]
The regression potential for this fix should be very low, as it's a direct cherry-pick from upstream systemd. It has seen extensive testing in both upstream and other Ubuntu releases, and was verified for Bionic through autopkgtests.
================================
[Original Description]
It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail.
systemd version the issue has been seen with
Installed: 237-3ubuntu10.13
Used distribution
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
Expected behaviour you didn't see
Return A record for a domain when it exists.
Unexpected behaviour you saw
Resolution failed.
Steps to reproduce the problem
Whait for 1 minutes (github.com TTL for A record)
Try to resolv github.com CNAME record dig CNAME github.com
This will return an empty result.
Then try to resolve github.com A record dig A github.com.
This will now return empty result unless you restart systemd-resolved or wait for cache expiration.
At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8.
Exemple :
Wait for 1 minutes to let cache expire, then run
dig CNAME github.com
dig A github.com
# no result
dig A github.com @8.8.8.8
# ;; ANSWER SECTION:
# github.com. 59 IN A 192.30.253.113
# github.com. 59 IN A 192.30.253.112
PS: Don't forget to restart systemd-resolve, before trying to post an answer.
This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. |
|
| 2019-06-13 12:32:13 |
Łukasz Zemczak |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-06-13 12:32:16 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-06-13 12:32:17 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-06-13 12:32:21 |
Łukasz Zemczak |
tags |
sts sts-sponsor systemd |
sts sts-sponsor systemd verification-needed verification-needed-bionic |
|
| 2019-06-14 20:07:52 |
Heitor Alves de Siqueira |
tags |
sts sts-sponsor systemd verification-needed verification-needed-bionic |
sts sts-sponsor systemd verification-done-bionic verification-needed |
|
| 2019-06-18 21:14:49 |
Heitor Alves de Siqueira |
tags |
sts sts-sponsor systemd verification-done-bionic verification-needed |
sts sts-sponsor systemd verification-done verification-done-bionic |
|
| 2019-06-20 22:28:20 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-06-20 22:28:27 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-07-15 07:56:21 |
Andrea Ieri |
bug |
|
|
added subscriber Canonical IS BootStack |
| 2019-10-18 08:53:24 |
Jeremy |
bug |
|
|
added subscriber Jeremy |
