[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid
Noticed this as well. I saw the iscsid daemon running on my systems, but found out that these were installed by default. root@sat01:~# apt remove open-iscsi Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic linux-headers-4.4.0-63 linux-headers-4.4.0-63-generic linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic Use 'apt autoremove' to remove them. The following packages will be REMOVED: open-iscsi ubuntu-server This should be modified that open-iscsi is not installed by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1630946 Title: ubuntu-server depends on open-iscsi and runs iscsid Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: ubuntu-server has a hard dependency on open-iscsi, which means there is a daemon running (iscsid), and the package cannot be removed. All unnecessary daemons are a cause of concern when auditing a system. Propose moving this to "Recommends" instead, which currently has: Recommends: lxd, snapd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-server 1.361 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 6 10:43:04 2016 Ec2AMI: ami-c06b1eb3 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1630946/+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
[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
0.8.11 is out now in Ubuntu and has these fixes. Ubuntu 16.04 LTS is now released with this bug in there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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
[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
The patch has been accepted upstream: https://anonscm.debian.org/cgit /collab- maint/ifupdown.git/commit/?id=bfca5654959d27603eb50747d9998b92f1d7eb41 Version 0.8.11 should be released soon which should fix this issue. Ubuntu can then fetch this from upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Confirmed Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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
[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
I have sent a patch for this upstream to Debian. Waiting for it to get accepted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Confirmed Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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
[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
I just ran into the same issue on a 16.04 system in a IPv6-only network. My network configuration looks like this: auto eno1 iface eno1 inet6 dhcp The fix posted by Graham works for me. After modifying that line I succesfully get DHCPv6 after a clean reboot. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Confirmed Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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
