** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
       Status: Confirmed

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Description changed:

+ [impact]
+ 
+ dhclient fails to notify resolved about DNS servers due to bash-specific
+ redirect inside 'resolved' hook script
+ 
+ [test case]
+ 
+ see original description below
+ 
+ [regression potential]
+ 
+ any regression would likely cause resolved not to be aware of dhclient-
+ provided dns servers
+ 
+ [other info]
+ 
+ This is needed only in Eoan and later; X/B/D do not have the bash-
+ specific redirect '&>' in their hook file.
+ 
+ original description:
+ ---
+ 
+ 
  The file /etc/dhcp/dhclient-enter-hooks.d/resolved
  provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due 
to systemd-resolved is not run.
  This issue can be reproduced on Ubuntu Eoan:
  ==============================
- root@eoan:~# dhclient -v 
+ root@eoan:~# dhclient -v
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  
  Listening on LPF/ens224/00:0c:29:92:d4:da
  Sending on   LPF/ens224/00:0c:29:92:d4:da
  Listening on LPF/ens192/00:0c:29:92:d4:d0
  Sending on   LPF/ens192/00:0c:29:92:d4:d0
  Listening on LPF/ens160/00:0c:29:92:d4:c6
  Sending on   LPF/ens160/00:0c:29:92:d4:c6
  Sending on   Socket/fallback
  DHCPDISCOVER on ens224 to 255.255.255.255 port 67 interval 3 (xid=0x6d9fb33d)
  DHCPDISCOVER on ens192 to 255.255.255.255 port 67 interval 3 (xid=0xeb8fda26)
  DHCPREQUEST for 192.168.120.4 on ens160 to 255.255.255.255 port 67 
(xid=0x6d39545d)
  DHCPACK of 192.168.120.4 from 192.168.120.254 (xid=0x5d54396d)
  RTNETLINK answers: File exists
  d41d8cd98f00b204e9800998ecf8427e  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  5025823d750dda1f3f15e306c4a0afce  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  bound to 192.168.120.4 -- renewal in 111 seconds.
  root@eoan:~# resolvectl status |grep DNS
  MulticastDNS setting: no
-   DNSOverTLS setting: no
-       DNSSEC setting: no
-     DNSSEC supported: no
-           DNSSEC NTA: 10.in-addr.arpa
+   DNSOverTLS setting: no
+       DNSSEC setting: no
+     DNSSEC supported: no
+           DNSSEC NTA: 10.in-addr.arpa
  MulticastDNS setting: no
-   DNSOverTLS setting: no
-       DNSSEC setting: no
-     DNSSEC supported: no
+   DNSOverTLS setting: no
+       DNSSEC setting: no
+     DNSSEC supported: no
  MulticastDNS setting: no
-   DNSOverTLS setting: no
-       DNSSEC setting: no
-     DNSSEC supported: no
+   DNSOverTLS setting: no
+       DNSSEC setting: no
+     DNSSEC supported: no
  MulticastDNS setting: no
-   DNSOverTLS setting: no
-       DNSSEC setting: no
-     DNSSEC supported: no
+   DNSOverTLS setting: no
+       DNSSEC setting: no
+     DNSSEC supported: no
  ==============================
  
  Attached please find the patch for this. The output for md5sum in the
  hook file resolv should separate the stdout and stderr so it won't
  compare the wrong data.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849608

Title:
  systemd resolv should separate the output of stdout and stderr

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Eoan:
  New
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  dhclient fails to notify resolved about DNS servers due to bash-
  specific redirect inside 'resolved' hook script

  [test case]

  see original description below

  [regression potential]

  any regression would likely cause resolved not to be aware of
  dhclient-provided dns servers

  [other info]

  This is needed only in Eoan and later; X/B/D do not have the bash-
  specific redirect '&>' in their hook file.

  original description:
  ---

  
  The file /etc/dhcp/dhclient-enter-hooks.d/resolved
  provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due 
to systemd-resolved is not run.
  This issue can be reproduced on Ubuntu Eoan:
  ==============================
  root@eoan:~# dhclient -v
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens224/00:0c:29:92:d4:da
  Sending on   LPF/ens224/00:0c:29:92:d4:da
  Listening on LPF/ens192/00:0c:29:92:d4:d0
  Sending on   LPF/ens192/00:0c:29:92:d4:d0
  Listening on LPF/ens160/00:0c:29:92:d4:c6
  Sending on   LPF/ens160/00:0c:29:92:d4:c6
  Sending on   Socket/fallback
  DHCPDISCOVER on ens224 to 255.255.255.255 port 67 interval 3 (xid=0x6d9fb33d)
  DHCPDISCOVER on ens192 to 255.255.255.255 port 67 interval 3 (xid=0xeb8fda26)
  DHCPREQUEST for 192.168.120.4 on ens160 to 255.255.255.255 port 67 
(xid=0x6d39545d)
  DHCPACK of 192.168.120.4 from 192.168.120.254 (xid=0x5d54396d)
  RTNETLINK answers: File exists
  d41d8cd98f00b204e9800998ecf8427e  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  5025823d750dda1f3f15e306c4a0afce  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  bound to 192.168.120.4 -- renewal in 111 seconds.
  root@eoan:~# resolvectl status |grep DNS
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
            DNSSEC NTA: 10.in-addr.arpa
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
        DNSSEC setting: no
      DNSSEC supported: no
  ==============================

  Attached please find the patch for this. The output for md5sum in the
  hook file resolv should separate the stdout and stderr so it won't
  compare the wrong data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849608/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to