[Bug 1756040] Re: bionic: LXD containers don't get fan network IP addresses

This is bionic top to bottom. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1756040 Title: bionic: LXD containers don't get fan network IP addresses To manage notifications about

[Bug 1753018] Re: Please merge strongswan 5.6.2-1 from Debian

FYI, the CVE was already fixed in 5.6.1-2ubuntu4. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1753018 Title: Please merge strongswan 5.6.2-1 from Debian To manage notifications

[Bug 1752352] Re: symbolic links are blinking with byobu

** Changed in: byobu Status: Confirmed => Fix Committed ** Changed in: byobu (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to byobu in Ubuntu. https://bugs.launchpad.net/bugs/1752352

[Bug 1756040] [NEW] bionic: LXD containers don't get fan network IP addresses

Public bug reported: Juju Version: 2.3.4 Substrate: OpenStack I'm deploying a bundle which makes use of LXD containers, leveraging fan networking for communication between containers and hosts; containers start and have the following config snippet: devices: eth0: hwaddr:

[Bug 1756032] [NEW] No VPN connectivity when accessing tunnel endpoint over IPv6

Public bug reported: Our VPN provides both IPv4 and IPv6 addresses for the tunnel endpoint. With the latest openvpn on Bionic, the VPN starts, but no network connectivity is actually established if the client is accessing from an IPv6 enabled location; forcing the tunnel endpoint to IPv4 (using

[Bug 1755383] Re: package samba 2:4.6.7+dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thanks for filing this bug in Ubuntu. Unfortunately there is not enough information in the attached logs to determine why the service restart failed at the postinst stage. Please attach the samba log files from /var/log/samba/log* as they may have more details. Thanks ** Changed in: samba

[Bug 1755657] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thanks for filing this bug in Ubuntu. Unfortunately there isn't enough information in the attached logs about what happened. Please attach the log files from /var/log/samba/log* as they may have further information. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You

[Bug 1755657] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details. invoke-rc.d: initscript smbd, action "start" failed. ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded

[Bug 1754981] Re: Could not open 'local/usr.sbin.named'

Confirmed: Mar 15 12:48:12 bionic-bind9 apparmor[1859]: AppArmor parser error for /etc/apparmor.d/usr.sbin.named in /etc/apparmor.d/usr.sbin.named at line 69: Could not open 'local/usr.sbin.named' Mar 15 12:48:12 bionic-bind9 apparmor[1859]: Skipping profile in /etc/apparmor.d/disable:

[Bug 1754981] Re: Could not open 'local/usr.sbin.named'

** Changed in: bind9 (Ubuntu) Status: Triaged => In Progress ** Bug watch added: Debian Bug tracker #893005 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893005 ** Also affects: bind9 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893005 Importance: Unknown