[Sts-sponsors] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.
I've been told that the "resume" doesn't resume boot. Can someone validate ? -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: In Progress Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: In Progress Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Invalid Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : sts-sponsors@lists.launchpad.net Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf
** Tags removed: sts-sru-needed verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: sts-sru-done verification-done verification-done-bionic
verification-done-xenial
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1791108
Title:
open-iscsi uses domainsearch instead of search for /etc/resolv.conf
Status in open-iscsi package in Ubuntu:
Fix Released
Status in open-iscsi source package in Xenial:
Fix Committed
Status in open-iscsi source package in Bionic:
Fix Committed
Status in open-iscsi source package in Cosmic:
Fix Released
Bug description:
[Impact]
* open-iscsi is adding "domainsearch", a non-existent configuration
option, instead of "search" in /etc/resolv.conf. As a result, the
search list is ignored in the clients.
[Test case]
* Install an ubuntu machine that uses iscsi as root, and does not use
systemd-resolvd.
* Prepare the dhcp server to provide the search list to its clients. For
instance, in dnsmasq:
dhcp-option=option:domain-search,canonical.com
* Boot the machine and check the content of /etc/resolv.conf
- if domainsearch is present, the search list will be ignored:
root@iscsi-xenial:/home/ubuntu# ping -c1 golem
ping: unknown host golem
root@iscsi-xenial:/home/ubuntu# strace ping -c1 golem 2>&1 | grep golem
execve("/bin/ping", ["ping", "-c1", "golem"], [/* 19 vars */]) = 0
sendto(4, "_(\1\0\0\1\0\0\0\0\0\0\5golem\0\0\1\0\1", 23, MSG_NOSIGNAL, NULL,
0) = 23
recvfrom(4, "_(\201\203\0\1\0\0\0\0\0\0\5golem\0\0\1\0\1", 1024, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.122.1")},
[16]) = 23
write(2, "ping: unknown host golem\n", 25ping: unknown host golem
- if search is present, the search list will be used:
root@iscsi-xenial:/home/ubuntu# ping -c1 golem
PING golem.canonical.com (91.189.89.199) 56(84) bytes of data.
64 bytes from golem.canonical.com (91.189.89.199): icmp_seq=1 ttl=57
time=63.7 ms
--- golem.canonical.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 63.735/63.735/63.735/0.000 ms
root@iscsi-xenial:/home/ubuntu# strace ping -c1 golem 2>&1 | grep golem
execve("/bin/ping", ["ping", "-c1", "golem"], [/* 19 vars */]) = 0
sendto(4, "\1\\\1\0\0\1\0\0\0\0\0\0\5golem\tcanonical\3com"..., 37,
MSG_NOSIGNAL, NULL, 0) = 37
recvfrom(4, "\1\\\201\200\0\1\0\1\0\0\0\0\5golem\tcanonical\3com"..., 1024,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [16]) = 53
write(1, "PING golem.canonical.com (91.189"..., 145PING golem.canonical.com
(91.189.89.199) 56(84) bytes of data.
64 bytes from golem.canonical.com (91.189.89.199): icmp_seq=1 ttl=57
time=63.5 ms
write(1, "--- golem.canonical.com ping sta"..., 157--- golem.canonical.com
ping statistics ---
[Regression potential]
* The change is minor (a string replacement) and it's currently not working.
* Any possible regression would involve continuing to break DNS resolution.
[Other info]
* resolv.conf man page: http://man7.org/linux/man-
pages/man5/resolv.conf.5.html
[Original description]
Having an interface file such as /run/net-eno2.conf with the following
content:
DEVICE='eno2'
PROTO='dhcp'
IPV4ADDR='10.10.10.10'
IPV4BROADCAST='10.10.10.255'
IPV4NETMASK='255.255.255.0'
IPV4GATEWAY='10.10.10.1'
IPV4DNS0='169.254.169.254'
IPV4DNS1='0.0.0.0'
HOSTNAME=''
DNSDOMAIN='test.com'
NISDOMAIN=''
ROOTSERVER='169.254.169.254'
ROOTPATH=''
filename='/ipxe.efi'
UPTIME='45'
DHCPLEASETIME='86400'
DOMAINSEARCH='test.com'
net-interface-handler translates it to:
nameserver 169.254.169.254
domainsearch test.com
instead of:
nameserver 169.254.169.254
search test.com
The problem is that domainsearch is not a valid configuration option
for /etc/resolv.conf and is ignored.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1791108/+subscriptions
--
Mailing list: https://launchpad.net/~sts-sponsors
Post to : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help : https://help.launchpad.net/ListHelp
[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf
#VERIFICATION-BIONIC
- Before the update
ubuntu@iscsi-bionic:~$ dpkg -l | grep open-iscsi
ii open-iscsi2.0.874-5ubuntu2.2
amd64iSCSI initiator tools
ubuntu@iscsi-bionic:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 192.168.122.1
domainsearch example.com
ubuntu@iscsi-bionic:~$ sudo strace ping -c1 www 2>&1 | grep www
execve("/bin/ping", ["ping", "-c1", "www"], 0x7ffeb4aecd70 /* 14 vars */) = 0
sendmmsg(5, [{msg_hdr={msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\300\17\1\0\0\1\0\0\0\0\0\0\3www\0\0\1\0\1", iov_len=21}],
msg_iovlen=1, msg_controllen=0,
msg_flags=MSG_TRUNC|MSG_DONTWAIT|MSG_EOR|MSG_WAITALL|MSG_CONFIRM|MSG_RST|MSG_MORE|MSG_BATCH|MSG_ZEROCOPY|MSG_FASTOPEN|0xb42},
msg_len=21}, {msg_hdr={msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\0\31\1\0\0\1\0\0\0\0\0\0\3www\0\0\34\0\1", iov_len=21}],
msg_iovlen=1, msg_controllen=0,
msg_flags=MSG_CTRUNC|MSG_FIN|MSG_SYN|MSG_CONFIRM|MSG_RST|MSG_MORE|MSG_BATCH|MSG_ZEROCOPY|MSG_FASTOPEN|0xb420010},
msg_len=21}], 2, MSG_NOSIGNAL) = 2
recvfrom(5, "\300\17\201\203\0\1\0\0\0\0\0\0\3www\0\0\1\0\1", 2048, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.122.1")},
[28->16]) = 21
recvfrom(5,
"\0\31\201\203\0\1\0\0\0\1\0\0\3www\0\0\34\0\1\0\0\6\0\1\0\0\"L\0@"..., 65536,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [28->16]) = 96
write(2, "ping: www: Name or service not k"..., 37ping: www: Name or service
not known
- After the update
ubuntu@iscsi-bionic:~$ dpkg -l | grep open-iscsi
ii open-iscsi2.0.874-5ubuntu2.3
amd64iSCSI initiator tools
ubuntu@iscsi-bionic:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 192.168.122.1
search example.com
ubuntu@iscsi-bionic:~$ sudo strace ping -c1 www 2>&1 | grep www
execve("/bin/ping", ["ping", "-c1", "www"], 0x7ffea5cd0390 /* 14 vars */) = 0
sendmmsg(5, [{msg_hdr={msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\262\224\1\0\0\1\0\0\0\0\0\0\3www\7example\3com\0\0\1\0"...,
iov_len=33}], msg_iovlen=1, msg_controllen=0,
msg_flags=MSG_TRUNC|MSG_DONTWAIT|MSG_EOR|MSG_WAITALL|MSG_CONFIRM|MSG_ERRQUEUE|MSG_NOSIGNAL|MSG_MORE|MSG_BATCH|MSG_ZEROCOPY|MSG_CMSG_CLOEXEC|0x1b48},
msg_len=33}, {msg_hdr={msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\226\235\1\0\0\1\0\0\0\0\0\0\3www\7example\3com\0\0\34\0"...,
iov_len=33}], msg_iovlen=1, msg_controllen=0,
msg_flags=MSG_CTRUNC|MSG_FIN|MSG_SYN|MSG_CONFIRM|MSG_ERRQUEUE|MSG_NOSIGNAL|MSG_MORE|MSG_BATCH|MSG_ZEROCOPY|MSG_CMSG_CLOEXEC|0x1b480010},
msg_len=33}], 2, MSG_NOSIGNAL) = 2
recvfrom(5, "\262\224\201\200\0\1\0\1\0\0\0\0\3www\7example\3com\0\0\1\0"...,
2048, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [28->16]) = 49
recvfrom(5, "\226\235\201\200\0\1\0\1\0\2\0\4\3www\7example\3com\0\0\34\0"...,
65536, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [28->16]) = 197
write(1, "PING www.example.com (93.184.216"..., 132PING www.example.com
(93.184.216.34) 56(84) bytes of data.
write(1, "--- www.example.com ping statist"..., 114--- www.example.com ping
statistics ---
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1791108
Title:
open-iscsi uses domainsearch instead of search for /etc/resolv.conf
Status in open-iscsi package in Ubuntu:
Fix Released
Status in open-iscsi source package in Xenial:
Fix Committed
Status in open-iscsi source package in Bionic:
Fix Committed
Status in open-iscsi source package in Cosmic:
Fix Released
Bug description:
[Impact]
* open-iscsi is adding "domainsearch", a non-existent configuration
option, instead of "search" in /etc/resolv.conf. As a result, the
search list is ignored in the clients.
[Test case]
* Install an ubuntu machine that uses iscsi as root, and does not use
systemd-resolvd.
* Prepare the dhcp server to provide the search list to its clients. For
instance, in dnsmasq:
dhcp-option=option:domain-search,canonical.com
* Boot the machine and check the content of /etc/resolv.conf
- if domainsearch is present, the search list will be ignored:
root@iscsi-xenial:/home/ubuntu# ping -c1 golem
ping: unknown host golem
root@iscsi-xenial:/home/ubuntu# strace ping -c1 golem 2>&1 | grep golem
execve("/bin/ping",
[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf
#VERIFICATION-XENIAL
- Before the update
ubuntu@iscsi_base:~$ dpkg -l | grep open-iscsi
ii open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3.5
amd64iSCSI initiator tools
ubuntu@iscsi_base:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.1
domainsearch example.com
ubuntu@iscsi_base:~$ strace ping -c1 www 2>&1 | grep www
execve("/bin/ping", ["ping", "-c1", "www"], [/* 20 vars */]) = 0
sendto(3, "=\370\1\0\0\1\0\0\0\0\0\0\3www\0\0\1\0\1", 21, MSG_NOSIGNAL, NULL,
0) = 21
recvfrom(3,
"=\370\201\203\0\1\0\0\0\1\0\0\3www\0\0\1\0\1\0\0\6\0\1\0\0*0\0@"..., 1024, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.122.1")},
[16]) = 96
write(2, "ping: unknown host www\n", 23ping: unknown host www
- After the update
ubuntu@iscsi_base:~$ dpkg -l | grep open-iscsi
ii open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3.6
amd64iSCSI initiator tools
ubuntu@iscsi_base:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.122.1
search example.com
ubuntu@iscsi_base:~$ strace ping -c1 www 2>&1 | grep www
execve("/bin/ping", ["ping", "-c1", "www"], [/* 20 vars */]) = 0
sendto(3, "\241\223\1\0\0\1\0\0\0\0\0\0\3www\7example\3com\0\0\1\0"..., 33,
MSG_NOSIGNAL, NULL, 0) = 33
recvfrom(3, "\241\223\201\200\0\1\0\1\0\0\0\0\3www\7example\3com\0\0\1\0"...,
1024, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [16]) = 49
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1791108
Title:
open-iscsi uses domainsearch instead of search for /etc/resolv.conf
Status in open-iscsi package in Ubuntu:
Fix Released
Status in open-iscsi source package in Xenial:
Fix Committed
Status in open-iscsi source package in Bionic:
Fix Committed
Status in open-iscsi source package in Cosmic:
Fix Released
Bug description:
[Impact]
* open-iscsi is adding "domainsearch", a non-existent configuration
option, instead of "search" in /etc/resolv.conf. As a result, the
search list is ignored in the clients.
[Test case]
* Install an ubuntu machine that uses iscsi as root, and does not use
systemd-resolvd.
* Prepare the dhcp server to provide the search list to its clients. For
instance, in dnsmasq:
dhcp-option=option:domain-search,canonical.com
* Boot the machine and check the content of /etc/resolv.conf
- if domainsearch is present, the search list will be ignored:
root@iscsi-xenial:/home/ubuntu# ping -c1 golem
ping: unknown host golem
root@iscsi-xenial:/home/ubuntu# strace ping -c1 golem 2>&1 | grep golem
execve("/bin/ping", ["ping", "-c1", "golem"], [/* 19 vars */]) = 0
sendto(4, "_(\1\0\0\1\0\0\0\0\0\0\5golem\0\0\1\0\1", 23, MSG_NOSIGNAL, NULL,
0) = 23
recvfrom(4, "_(\201\203\0\1\0\0\0\0\0\0\5golem\0\0\1\0\1", 1024, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.122.1")},
[16]) = 23
write(2, "ping: unknown host golem\n", 25ping: unknown host golem
- if search is present, the search list will be used:
root@iscsi-xenial:/home/ubuntu# ping -c1 golem
PING golem.canonical.com (91.189.89.199) 56(84) bytes of data.
64 bytes from golem.canonical.com (91.189.89.199): icmp_seq=1 ttl=57
time=63.7 ms
--- golem.canonical.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 63.735/63.735/63.735/0.000 ms
root@iscsi-xenial:/home/ubuntu# strace ping -c1 golem 2>&1 | grep golem
execve("/bin/ping", ["ping", "-c1", "golem"], [/* 19 vars */]) = 0
sendto(4, "\1\\\1\0\0\1\0\0\0\0\0\0\5golem\tcanonical\3com"..., 37,
MSG_NOSIGNAL, NULL, 0) = 37
recvfrom(4, "\1\\\201\200\0\1\0\1\0\0\0\0\5golem\tcanonical\3com"..., 1024,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("192.168.122.1")}, [16]) = 53
write(1, "PING golem.canonical.com (91.189"..., 145PING golem.canonical.com
(91.189.89.199) 56(84) bytes of data.
64 bytes from golem.canonical.com (91.189.89.199): icmp_seq=1 ttl=57
time=63.5 ms
write(1, "--- golem.canonical.com ping sta"..., 157--- golem.canonical.com
ping statistics ---
[Regression potential]
* The change is minor (a string replacement) and it's currently not working.
* Any possible regression would involve continuing to break DNS resolution.
[Other info]
* resolv.conf man page: http://man7.org/linux/man-
pages/man5/resolv.conf.5.html
[Original description]
Having an interface file such as /run/net-eno2.conf with the following
content:
DEVICE='eno2'
PROTO='dhcp'
IPV4ADDR='10.10.10.10'
IPV4BROADCAST='10.10.10.255'
IPV4NETMASK='255.255.255.0'
