[Kernel-packages] [Bug 1616949] Re: guest on bridge becomes inaccessible
** Tags added: jujuqa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616949 Title: guest on bridge becomes inaccessible Status in linux package in Ubuntu: Confirmed Bug description: We have a "virtual maas" setup where we have a maas node on a linux bridge (created by libvirt) and some other number of nodes on that same bridge. the maas node then controls the other nodes turning them on and off and generally working maas-like magic. In this scenario on 16.04 with when deploying 3 or so nodes at a time, the maas node becomes inaccessible, and as it is the root device for iscsi storage of the installs, the nodes fail also. This occurred with xenial kernel (4.4). Reverting the kernel to 3.19 (linux-lts-vivid) kernel fixes the problem. https://launchpad.net/ubuntu/+source/linux-lts-vivid Specifically, the fixed kernel is $ dpkg-query --show | grep linux-.*3.19 linux-image-3.19.0-66-generic 3.19.0-66.74~14.04.1 linux-image-extra-3.19.0-66-generic 3.19.0-66.74~14.04.1 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-66-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 25 12:10 seq crw-rw 1 root audio 116, 33 Aug 25 12:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 25 14:37:07 2016 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0 ProcLoadAvg: 0.40 0.28 0.46 1/1337 140794 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 3.19.0-66-generic (buildd@bos01-ppc64el-021) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #74~14.04.1-Ubuntu SMP Tue Jul 19 19:54:47 UTC 2016 RelatedPackageVersions: linux-restricted-modules-3.19.0-66-generic N/A linux-backports-modules-3.19.0-66-generic N/A linux-firmware 1.157.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.667 GHz (cpu 120) max: 3.691 GHz (cpu 0) avg: 3.689 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1402763] Re: Multicast traffic not propating correctly over linux bridge
** Tags added: lxc network ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1402763 Title: Multicast traffic not propating correctly over linux bridge Status in juju-core: Triaged Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: There's a lot of supposition in the title of this bug but its currently my best guess. In this deployment, I have a number of services running in LXC containers across multiple physical hosts; each service is clustered across three units, all on separate physical hosts, using corosync and pacemaker; when using multicast to support cluster communication, I occasionally see a container drop out of the cluster and use its isolation response (to shutdown all managed services); when using unicast I've not yet see this same problem. LXC containers are bridged to the main physical network using a linux bridge: eth0 - juju-br0 - vethXXX - | vethXXX | All MTU's are standard (1500). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.6-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Dec 15 17:20:08 2014 ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 17 10:16 seq crw-rw 1 root audio 116, 33 Dec 17 10:16 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: lxc 1.0.6-0ubuntu0.1 PackageArchitecture: amd64 PciMultimedia: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=5a86874d-8bbd-4e7a-b73e-17c914de390b ro ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images trusty uec-images apparmor Uname: Linux 3.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo video _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dmi.bios.date: 08/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.0.7 dmi.board.name: 0F0XJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.0.7:bd08/18/2011:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0F0XJ6:rvrA11:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1402763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages
** Changed in: juju-core Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1293549 Title: Filesystem mount from lxc template causes filesystem permission breakages Status in juju-core: Fix Released Status in lxc containers: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “postgresql” package in Juju Charms Collection: New Bug description: In juju-core 1.17.5, creating new lxc machines is now much faster as it appears to be using a template machine. In addition, the root filesystem is mounted from the template machine. Unfortunately, this causes filesystem permissions to screw up. juju deploy ubuntu juju ssh ubuntu/0 sudo chown ubuntu:ubuntu /etc/ssl/private ls /etc/ssl/private That final 'ls' fails with a permission denied. This is possibly a security precaution in lxc or the filesystem. This issue breaks the postgresql charm. The PostgreSQL packages require and use the ssl-cert package, which changes /etc/ssl/private to be group readable by the ssl-cert group. The postgres user, a member of the ssl-cert group, is unable to read the private key stored in this directory. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1293549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
