[Touch-packages] [Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
This is still a problem in 18.04. Like the OP, I have localhosts on my LAN, but have no local domain configured. I had to disable systemd- resolved on each of my LXC containers. What's worse, resolvconf creates an empty /etc/resolv.conf file. So I had to create resolv.conf by hand and point to DNS. Again, on each of my containers. This is a major regression. If the systemd-resolved is to be kept, at least have some decency to explicitly note in 18.04 LTS release notes that local hostname resolution requires local domain to be configured for name resolution to work. -- 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/1699660 Title: systemd-resolve breaks resolution of local network hostnames Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04 (zesty), resolution of my local network's host names is completely broken. Apparently the upgrade replaced my existing resolver with systemd-resolve, which deliberately refuses to pass "single-label" domain names to my domain name server. That is the server where all my network's host names are kept, so I can no longer resolve any of them. Apparently, this is yet another example of Poettering's upstream decisions causing denial of service to people who have been saddled with his malware. https://github.com/systemd/systemd/issues/2514#issuecomment-179203186 Would someone sensible please put a stop to this forced breakage during upgrade, and advise on how to fix it now that the damage has been done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+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 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40
Yes it is, at 1.79ubuntu9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1762899 Title: /etc/resolv.conf empty after upgrading from 16.04 to 18.40 Status in resolvconf package in Ubuntu: Incomplete Bug description: I just upgraded one of my LXC containers to 18.04 and after rebooting, the /etc/resolv.conf contains no nameservers. systemd-resolve, however, resolves fine and the --status returns the DNS server details as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Tue Apr 10 22:53:30 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1762899] [NEW] /etc/resolv.conf empty after upgrading from 16.04 to 18.40
Public bug reported: I just upgraded one of my LXC containers to 18.04 and after rebooting, the /etc/resolv.conf contains no nameservers. systemd-resolve, however, resolves fine and the --status returns the DNS server details as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Tue Apr 10 22:53:30 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1762899 Title: /etc/resolv.conf empty after upgrading from 16.04 to 18.40 Status in resolvconf package in Ubuntu: New Bug description: I just upgraded one of my LXC containers to 18.04 and after rebooting, the /etc/resolv.conf contains no nameservers. systemd-resolve, however, resolves fine and the --status returns the DNS server details as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Tue Apr 10 22:53:30 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1738085] Re: Bridge gets created while the network interfaces are still being renamed
Can anyone please acknowledge this issue and assign it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610365] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready And after the boot process completes, the bridge is not configured as requested: # brctl show bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan2 lan3 wlan rename7 8000.90e2baaee821 no lan1 Note that while the "rename7" name of the bridge seems to be constant, the interface bridged is not.
[Touch-packages] [Bug 1692111] Re: Unable to configure raw.id_map with multiple entries
Is there any chance this can get backported to Xenial? I can see this fix was included in 2.1.0-0ubuntu1, but the LTS package is still at 2.0.8-0ubuntu1~16.04.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1692111 Title: Unable to configure raw.id_map with multiple entries Status in lxc package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: I am trying to map two users (999, 1001) to one of my containers. I added both IDs to /etc/subgid and /etc/subuid. I followed by setting raw.id_map property value (as instructed here https://lists.linuxcontainers.org/pipermail/lxc- users/2017-March/013034.html): "echo -e "both 999 999\nboth 1001 1001" | lxc config set mycontainer raw.idmap -" However upon starting the container, I get errors (log excerpt below). If, on the other hand, I set idmap to either "both 999 999" or "both 1001 1001" only - i.e. if I map only one user at the time, the container starts just fine and the user is mapped as expected. My subgid and subuid look as follows: lxd:10:65536 root:10:65536 root:1001:1 root:999:1 Log excerpt: Name: mycontainer Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/02/22 18:54 UTC Status: Stopped Type: persistent Profiles: default Log: lxc 20170519204102.895 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer" already existed. lxc 20170519204102.896 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory lxc 20170519204102.897 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed. lxc 20170519204102.897 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory lxc 20170519204102.897 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed. lxc 20170519204102.898 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory lxc 20170519204102.898 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed. lxc 20170519204102.898 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory lxc 20170519204102.898 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed. lxc 20170519204102.898 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory lxc 20170519204102.899 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed. lxc 20170519204102.899 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory lxc 20170519204102.899 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed. lxc 20170519204102.899 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory lxc 20170519204102.900 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed. lxc 20170519204102.900 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory lxc 20170519204102.900 ERRORlxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path "/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed. lxc 20170519204102.900 ERRORlxc_cgfsng - cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to create /sys/fs/cgroup/systemd//lxc/mycontainer-8: No such file or directory lxc 20170519204102.901
[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
I previously said that the "rename7" bridge name seemed constant, but after playing around a bit today I noticed that it's not exactly so. For example, I just saw following bridge setup after restarting my server: bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan1 lan3 veth0P2CUY veth0QOJAX veth2MHFCX vethS3BS5A rename108000.90e2baaee820 no wlan rename7 8000.90e2baaee822 no lan2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2)
[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
** Also affects: bridge-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610365] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready And after the boot process completes, the bridge is not configured as requested: # brctl show bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan2 lan3 wlan rename7 8000.90e2baaee821 no lan1 Note that while the "rename7" name of the bridge seems to be constant, the
[Touch-packages] [Bug 1738085] [NEW] Bridge gets created while the network interfaces are still being renamed
Public bug reported: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610365] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready And after the boot process completes, the bridge is not configured as requested: # brctl show bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan2 lan3 wlan rename7 8000.90e2baaee821 no lan1 Note that while the "rename7" name of the bridge seems to be constant, the interface bridged is not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Wed Dec 13 16:11:11 2017 InstallationDate: Installed on 2016-07-28 (503 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8
[Touch-packages] [Bug 1654624] Re: dhcp apparmor profile complains about lxd client
** This bug is no longer a duplicate of bug 1660836 apparmor auditing denied access of special apparmor .null fi\ le -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1654624 Title: dhcp apparmor profile complains about lxd client Status in apparmor package in Ubuntu: Confirmed Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Hi, strange problem recently occured: I'm having some ubuntu machines running in LXD (nothing unusual, just based on the regular ubuntu LXD images) on a ubuntu host. Worked well for some time. But now the host generates messages like Jan 6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400 audit(1483726625.388:247): apparmor="DENIED" operation="file_perm" namespace="root//lxd-rackadmin_" profile="/sbin/dhclient" name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=165536 ouid=0 in /var/log/kern.log. For some reason the apparmor running on the host interferes with the containers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jan 6 19:19:12 2017 SourcePackage: isc-dhcp UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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 1654624] Re: dhcp apparmor profile complains about lxd client
*** This bug is a duplicate of bug 1660836 *** https://bugs.launchpad.net/bugs/1660836 ** This bug has been marked a duplicate of bug 1660836 apparmor auditing denied access of special apparmor .null fi\ le -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1654624 Title: dhcp apparmor profile complains about lxd client Status in apparmor package in Ubuntu: Confirmed Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Hi, strange problem recently occured: I'm having some ubuntu machines running in LXD (nothing unusual, just based on the regular ubuntu LXD images) on a ubuntu host. Worked well for some time. But now the host generates messages like Jan 6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400 audit(1483726625.388:247): apparmor="DENIED" operation="file_perm" namespace="root//lxd-rackadmin_" profile="/sbin/dhclient" name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=165536 ouid=0 in /var/log/kern.log. For some reason the apparmor running on the host interferes with the containers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jan 6 19:19:12 2017 SourcePackage: isc-dhcp UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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 1573359] Re: No wireless networks after starting system
Fresh after booting, following is suspicious in syslog: dell kernel: [9.232325] brcmf_add_if: ERROR: netdev:wlp58s0 already exists dell kernel: [9.232347] brcmf_add_if: ignore IF event and in dmesg: [9.232325] brcmf_add_if: ERROR: netdev:wlp58s0 already exists [9.232347] brcmf_add_if: ignore IF event [9.236112] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [9.242258] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [9.246334] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready After restarting nm service, dmesg says: [ 168.481449] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 168.685438] userif-2: sent link down event. [ 168.685442] userif-2: sent link up event. [ 168.793376] brcmf_add_if: ERROR: netdev:wlp58s0 already exists [ 168.793380] brcmf_add_if: ignore IF event [ 168.828171] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 175.118508] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573359 Title: No wireless networks after starting system Status in network-manager package in Ubuntu: New Bug description: After booting the system, there are no networks reported in Network Manager applet. After restarting network-manager service, it picks up the pre-configigured network and connects straight away. This has not been like this before and only started about 2 weeks ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 22:29:46 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.16.53.0/24 dev vmnet1 proto kernel scope link src 172.16.53.1 172.16.138.0/24 dev vmnet8 proto kernel scope link src 172.16.138.1 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.202 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-03-23 (29 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 you_gonna_make_me_pregnant 1 991de0b1-f4d3-4ead-9706-bea9979248f5 /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573359/+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 1573359] [NEW] No wireless networks after starting system
Public bug reported: After booting the system, there are no networks reported in Network Manager applet. After restarting network-manager service, it picks up the pre-configigured network and connects straight away. This has not been like this before and only started about 2 weeks ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 22:29:46 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.16.53.0/24 dev vmnet1 proto kernel scope link src 172.16.53.1 172.16.138.0/24 dev vmnet8 proto kernel scope link src 172.16.138.1 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.202 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-03-23 (29 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 you_gonna_make_me_pregnant 1 991de0b1-f4d3-4ead-9706-bea9979248f5 /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573359 Title: No wireless networks after starting system Status in network-manager package in Ubuntu: New Bug description: After booting the system, there are no networks reported in Network Manager applet. After restarting network-manager service, it picks up the pre-configigured network and connects straight away. This has not been like this before and only started about 2 weeks ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 22:29:46 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (1094 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.16.53.0/24 dev vmnet1 proto kernel scope link src 172.16.53.1 172.16.138.0/24 dev vmnet8 proto kernel scope link src 172.16.138.1 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.202 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-03-23 (29 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 you_gonna_make_me_pregnant 1 991de0b1-f4d3-4ead-9706-bea9979248f5 /org/freedesktop/NetworkManager/ActiveConnection/0 vmnet1 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- vmnet8 ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 --
[Touch-packages] [Bug 1560797] [NEW] package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Public bug reported: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: New Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+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
