[Bug 1761240] Re: SRU pollinate 4.31

I'd suggest modifying the test-case to skip the pollen side, the client we want to SRU will print the agent string it generates: # pollinate --print-user-agent cloud-init/18.2-4-g05926e48-0ubuntu1 curl/7.58.0-2ubuntu3 pollinate/4.31-0ubuntu1 Ubuntu/Bionic/Beaver/(development/branch)

[Bug 1762881] Re: cloud-init (18.2-0ubuntu1) does NOT detect the correct datasource after installed Ubuntu18.04 Beta2 Server on a VMWare VM

Booting a server image on VMware does not mean it uses the OVF datasource. You must provide an OVF to the image. If you believe that you did provide an OVF to the image, please attach the OVF iso and include the log file generated from: cloud-init collect-logs. ** Changed in: open-vm-tools

[Bug 1732002] Re: cloud images in lxc get ipv6 address

The MP has been moved to a github PR: https://github.com/CanonicalLtd/netplan/pull/19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732002 Title: cloud images in lxc get ipv6 address To manage

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

ubuntu@foufoune:~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ubuntu@foufoune:~$ apt-cache policy systemd systemd: Installed: 234-2ubuntu12.3 Candidate: 234-2ubuntu12.3 Version table: *** 234-2ubuntu12.3 500 500 http://azure.archive.ubuntu.com/ubuntu

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

I'm seeing this on Artful as well, in Azure cloud. ** Also affects: glibc (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided

[Bug 1759664] Re: sru curtin 2018-03-28 - 18.1-0ubuntu1

** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1757565] Re: btrfs and tar sparse truncate archives

Verified artful-proposed. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20180404 root@ubuntu:~# uname -a Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda

Re: [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

On Tue, Apr 10, 2018 at 2:44 AM, Colin Ian King <1760...@bugs.launchpad.net> wrote: > Would an immediate return with some error/warning message be more > appropriate that a 10 second delay? Yes. I would think that the amount of time to wait could be an option. I've read that in some scenarios

Re: [Bug 1732002] Re: cloud images in lxc get ipv6 address

Guys, I'm no longer suggesting that we disable RA here. After our discussion I updated this bug to indicate that we really want some way to *leave* RA alone. At this point that means netplan needs to *NOT* emit AcceptRA values into the .network configuration files by default (as it does now),

[Bug 1732002] Re: cloud images in lxc get ipv6 address

The kernel value is equivalent to not writing it out, yes; I thought it'd be better to be explicit in the config. W.r.t disabling by default; no plans to do so at this point but as it is now, all Artful and Bionic images will block for 10 seconds, unless an RA comes in sooner. So ideally we stop

[Bug 1761240] Re: SRU pollinate 4.31

** Also affects: pollinate (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug

[Bug 1761573] Re: Network not configured on bionic

Possibly related: https://bugzilla.redhat.com/show_bug.cgi?id=1525523 https://marc.info/?l=linux-kernel=151272209903675=2 That *should* be in bionic 4.15 ... and from the log, you're running 4.13. I suspect kernel bug on e1000e here. Can you boot with bionic 4.15 kernel and check again? --

[Bug 1761573] Re: Network not configured on bionic

So, what's happening here is the BOOTIF parameter specifies a MAC of a device, but that device is *not* found; then we see the errors here. So let's get confirmation that the BOOTIF parameter mac matches with one or more of the interfaces on the system. I recreated this same failure by booting a

[Bug 1761573] Re: Network not configured on bionic

Also can you provide a list of interfaces and their mac address values? Maybe the commissioning, lshw output? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761573 Title: Network not

[Bug 1761573] Re: Network not configured on bionic

Can you attach the xenial log that boots just fine on the same hardware? ** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1759664] Re: sru curtin 2018-03-28 - 18.1-0ubuntu1

** Attachment added: "curtin-vmtest-proposed-a-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+attachment/5102854/+files/curtin-vmtest-proposed-a-console.log ** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new

[Bug 1759664] Re: sru curtin 2018-03-28 - 18.1-0ubuntu1

** Attachment added: "curtin-vmtest-proposed-a-artifacts.tar.xz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+attachment/5102853/+files/curtin-vmtest-proposed-a-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1759664] Re: sru curtin 2018-03-28 - 18.1-0ubuntu1

** Attachment added: "curtin-vmtest-proposed-x-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+attachment/5102852/+files/curtin-vmtest-proposed-x-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1759664] Re: sru curtin 2018-03-28 - 18.1-0ubuntu1

** Attachment added: "xenial-proposed vmtest artifacts" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+attachment/5102851/+files/curtin-vmtest-proposed-x-artifacts.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade

As per cloud-init networking disabled. Please reopen task if you find cloud-init is in the picture here. ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64

I'm marking this bug as invalid as the scenario described is not valid. Installing cloud-init into a desktop image does not mean that cloud-init service will run; it's a boot time service that requires providing cloud-init a valid datasource. If you disagree, please reopen and provide further

[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64

> this issue doesn't exist in ubuntu-18.04-Server-64. The server image for 18.04 uses cloud-init during its initial boot as part of how the new server installer works; The desktop does not use cloud-init in any way; it is not expected to run desktop images; cloud- init is a boot-time service for

Re: [Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64

On Wed, Apr 4, 2018 at 5:44 AM, Pengpeng Sun <1760...@bugs.launchpad.net> wrote: > Yes, I saw 'No ds found [mode=search, notfound=disabled]. Disabled > cloud-init' from /run/cloud-init/ds-identify.log, will attach it. > > The Ubuntu Server is the server build I downloaded from below link and >

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Is this also fixed in bionic yet? On Tue, Apr 3, 2018 at 9:10 AM, Launchpad Bug Tracker <1729...@bugs.launchpad.net> wrote: > This bug was fixed in the package linux - 4.13.0-38.43 > > --- > linux (4.13.0-38.43) artful; urgency=medium > > * linux: 4.13.0-38.43 -proposed tracker (LP:

[Bug 1760776] Re: cloud-init (18.2-0ubuntu1) service is not running in ubuntu-18.04-desktop-64

You can also do: apport-collect 1760776 and cloud-init collect-logs # this writes a cloud-init.tar.gz to the current directory And attach those to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1760173] [NEW] zfs, zpool commands hangs for 10 seconds without a /dev/zfs

Public bug reported: 1. # lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 2. # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu19 Candidate: 0.6.5.6-0ubuntu19 Version table: *** 0.6.5.6-0ubuntu19 500 500

[Bug 1759080] [NEW] landscape-client generates dns queries for every ping operation

Public bug reported: 1. (kriek) ~ % lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 2. (kriek) ~ % apt-cache policy landscape-client landscape-client: Installed: 16.03-0ubuntu2.16.04.3 Candidate: 16.03-0ubuntu2.16.04.3 Version table: *** 16.03-0ubuntu2.16.04.3 500

[Bug 1757565] Re: btrfs and tar sparse truncate archives

Test kernel: GOOD root@ubuntu:~# cat /proc/version_signature Ubuntu 4.13.0-37.42~lp1757565-generic 4.13.13 root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp;

[Bug 1757565] Re: btrfs and tar sparse truncate archives

Yeah, rc2 was fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives To manage notifications about this bug go to:

[Bug 1757565] Re: btrfs and tar sparse truncate archives

This looks promising and landed in -rc2: Btrfs: fix reported number of inode blocks after buffered append writes https://www.spinics.net/lists/linux-btrfs/msg71274.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1757565] Re: btrfs and tar sparse truncate archives

v4.15-rc6: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc6-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp;

[Bug 1757565] Re: btrfs and tar sparse truncate archives

v4.15 Final: GOOD root@ubuntu:~# uname -r 4.15.0-041500-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp;

Re: [Bug 1757565] Re: btrfs and tar sparse truncate archives

On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisbury wrote: > @Scott, will that upstream commit make it so the kernel fix we are > looking for is not required? This is a curtin workaround; we're not using the sparse flag when invoking tar; However, the bug/issue

[Bug 1757565] Re: btrfs and tar sparse truncate archives

v4.15.7: GOOD root@ubuntu:~# uname -r 4.15.7-041507-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp

[Bug 1757565] Re: btrfs and tar sparse truncate archives

v4.14-rc1: BAD ubuntu@ubuntu:~$ uname -r 4.14.0-041400rc1-generic ubuntu@ubuntu:~$ sudo bash root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum

[Bug 1757565] Re: btrfs and tar sparse truncate archives

** Also affects: tar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives To manage

[Bug 1757565] [NEW] btrfs and tar sparse truncate archives

Public bug reported: root@ubuntu:~# lsb_release -rd Description:Ubuntu 17.10 Release:17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500

[Bug 1732002] Re: cloud images in lxc get ipv6 address

It would be nice for both nplan and networkd to accept a tri-state: accept-ra: [off|on|kernel] I think that would make it clear rather than an unset value to indicate that it's controlled by the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1732002] Re: cloud images in lxc get ipv6 address

After some discussion, it appears that networkd is kinda of making a boolean (on|off) for IPV6 RA, when it's really a tri-state (on|off|kernel). Upstream networkd indicates there is a tri-state; like so: Enable or disable IPv6 Router Advertisement (RA) reception support for the interface. Takes

[Bug 1756987] [NEW] chrony install does not stop systemd-timesyncd

Public bug reported: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 root@ubuntu:~# uname -a Linux ubuntu 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 2. root@ubuntu:~# apt-cache policy systemd

[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Xenial verified. root@ubuntu:~# lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 root@ubuntu:~# uname -a Linux ubuntu 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# apt-cache policy linux-image-virtual

[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Artful verified: ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ apt-cache policy linux-image-virtual

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Not sure if this was supposed to also be fixed in bionic-proposed yet, but I assumed so and it's not working there; I'll test -proposed in artful and xenial next. ubuntu@ubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu

[Bug 1754581] Re: trusty bcache NULL pointer exception

I think it may have always been present; I can recreate this on Trusty GA kernels; we've changed how we clean/remove bcache devices which I believe is triggering a new path on Trusty kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

Re: [Bug 1754581] Re: trusty bcache NULL pointer exception

On Fri, Mar 9, 2018 at 9:49 AM, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? I don't think so; how we're using/clearing/stopping bcache has

[Bug 1754581] [NEW] trusty bcache NULL pointer exception

Public bug reported: successfully wiped device /dev/md0 on attempt 1/4 shutdown running on holder type: 'bcache' syspath: '/sys/class/block/bcache0' stopping bcache cacheset at: /sys/fs/bcache/7834b3df-d029-49a3-9c1b-3fd628db10f2 waiting for /sys/fs/bcache/7834b3df-d029-49a3-9c1b-3fd628db10f2 to

[Bug 1753786] Re: mdadm-last-resort@.service runs when array is active

** Merge proposal linked: https://code.launchpad.net/~raharper/ubuntu/+source/mdadm/+git/mdadm/+merge/340951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753786 Title:

[Bug 1753786] Re: mdadm-last-resort@.service runs when array is active

** Bug watch added: Debian Bug tracker #892257 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892257 ** Also affects: mdadm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892257 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1753786] [NEW] mdadm-last-resort@.service runs when array is active

Public bug reported: In testing, a raid5 array is started and mounted, but at some point the mdadm-last-resort@md0.service is triggered and unmounts the raid device. This is fixed upstream with: https://github.com/neilbrown/mdadm/commit/5c4b3b9aa9f576305b36d5ccbd4b929b51307ce9 1.

[Bug 1752956] [NEW] netplan generate error message points to the wrong line number

Public bug reported: 1. root@b2:~# lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 root@b2:~# cat /etc/cloud/build.info build_name: server serial: 20180224 2. root@b2:~# apt-cache policy nplan nplan: Installed: 0.33 Candidate: 0.33

[Bug 1752162] [NEW] netplan 0.33 silently breaks bridge-priority

Public bug reported: 1. # lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 # cat /etc/cloud/build.info build_name: server serial: 20180224 2. # apt-cache policy nplan nplan: Installed: 0.33 Candidate: 0.33 Version table: *** 0.33 500

[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749722 Title: NTP: take into account

[Bug 1732002] Re: cloud images in lxc get ipv6 address

I've got a branch which would have cloud-init disable accept-ra unless cloud-init has an explicit ipv6 configuration (static or dhcp6). This only affects the solicitation effort, ipv6 link-local is of course, unaffected as is explicit ipv6 configuration. I believe LXD is in a position to know if

[Bug 1751176] [NEW] curtin exit codes broken by collect_logs misuse of sys.exit

Public bug reported: Currently any invocation of curtin that incurs an exception during the 'install' phase will trigger a path which runs the error log collection code. THere's a bug there which runs sys.exit() in the non-main body of the code; Instead only subcommands _main_ methods should

[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

I gave the "loopback" trick a go like so: root@b1:~# cat /etc/systemd/network/10-netplan-lo.network [Match] Name=lo [Network] Address=127.0.0.1 DNS=10.90.90.1 Domains=maaslab maas root@b1:~# networkctl status --all ● 1: lo Link File: n/a Network File:

Re: [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

On Thu, Feb 22, 2018 at 9:16 AM, Scott Moser wrote: > I dont think I really agree with this fix. > > I forgot that we dropped local-fs.target for exactly what we needed: After=systemd-remount-fs.service RequiresMountFor=/var/lib/cloud > Adding

Re: [Bug 1743643] Re: Install to dirty disk with swap fails

Can you: journalctl -b | grep -i "curtin: Installation started." That should dump the curtin version that was used; This is fixed in trunk but not yet uploaded to bionic. It's not clear how the live image obtains curtin, whether via the subiquity snap or using curtin from deb. On Wed, Feb

[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

So, definitely using the After=local-fs.target is a sane fix to ensuring that the local filesystem is mounted before starting. I'm interested in understanding why the open-vm-tools needs to run before cloud-init. specifically, what's wrong with: After=cloud-init.service which is when more of

Re: [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkov wrote: > I think cloud-init is the oracle of information of which ntp daemon to > use, and which ntp servers to use. Thus on bionic+ cloud-init, when > configuring ntp, should also "disable systemd-timesyncd" if some >

[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

Some further looking at the systemd side, Bionic no longer carries the override conf (disable-with-time-daemon.conf) in favor of updating each client's systemd unit to use: Conflicts=systemd-timesyncd.service Conflicts will ensure that the target service is stopped if the current unit is

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

On Fri, Feb 16, 2018 at 12:14 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > @raharper, I got side tracked and it got pushed down on my list. I can > still send it upstream if you want. It's currently in Ubuntu as a SAUCE > patch. > That would be great! Thanks, > > -- > You

[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

@jsalisbury Did you get a chance to forward the patch upstream? We've a userspace fix in the bcache-tools package for now; I've sent that upstream here: https://github.com/koverstreet/bcache-tools/pull/1 Kent was asking about the kernel fix, to which I pointed to the patch here. -- You

[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749722 Title: NTP: take into account systemd-timesyncd where present To

[Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID

** Description changed: + [Impact] + + * Current users of bcache devices may encounter unreliable device +numbering as the Linux kernel does not guarantee that bcache +minor numbers are assigned to the same devices at each boot. +Users who may have used /dev/bcacheN in paths to a

[Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID

** Merge proposal linked: https://code.launchpad.net/~raharper/ubuntu/+source/bcache-tools/+git/bcache-tools/+merge/337751 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728742 Title: curtin

[Bug 1728742] Re: curtin dname for bcache uses unstable devname instead of UUID

** Bug watch added: Debian Bug tracker #890446 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446 ** Also affects: bcache-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1735821] Re: netplan needs bridge port-priority support

FWIW, I tested the package in bionic-proposed and it passes the test I describe above: root@b2:~# netplan generate Error in network definition //etc/netplan/50-cloud-init.yaml line 19 column 16: unknown key port-priority root@b2:~# sudo vi /etc/apt/sources.list root@b2:~# sudo apt update && sudo

[Bug 1748332] Re: Bridges fail to come online when configured via LXD, netplan, and cloud-init

I suspect that since you provided no network configuration to the bridge, then it is considered unconfigured. networkctl seems to confirm. Now, it looks like we could use: BindCarrier= A link name or a list of link names. When set, controls the behavior of the current link. When all links in

[Bug 1747965] [NEW] cloud-init status reports done before boot is finished

Public bug reported: lxc launch ubuntu-daily:bionic b3 lxc exec b3 -- /bin/bash cloud-init status This returns 'done' even though cloud-final unit has not even started, typically cloud-init init mode=local has completed but we're waiting on networkd-wait-online to complete before cloud-config

[Bug 1747553] Re: dhcp allow client-identifier control

*** This bug is a duplicate of bug 1738998 *** https://bugs.launchpad.net/bugs/1738998 ** This bug has been marked a duplicate of bug 1738998 netplan does not allow dhcp client identifier type to be specified -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1747553] [NEW] dhcp allow client-identifier control

*** This bug is a duplicate of bug 1738998 *** https://bugs.launchpad.net/bugs/1738998 Public bug reported: In some cases, users of DHCP want to specify the client identifier. Under networkd, this can be toggled between mac and the RFC client id, from systemd-networkd documentation

[Bug 1747554] [NEW] cloud-init status in bionic stack traces

Public bug reported: 1. root@b2:~# lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. root@b2:~# apt-cache policy cloud-init cloud-init: Installed: 17.2-13-g6299e8d0-0ubuntu1 Candidate: 17.2-13-g6299e8d0-0ubuntu1 Version table: ***

[Bug 1747077] Re: curtainer needs to check installed version vs. source version

** Attachment added: "curtin-vmtest-daily-x-console.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1747077/+attachment/5047733/+files/curtin-vmtest-daily-x-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1747077] [NEW] curtainer needs to check installed version vs. source version

Public bug reported: When running ci tests, we encountered and error where the tests running were newer than the curtin used to handle the install. There was a small race with the archive, curtainer installed a binary package and the source package it pulled was one revision newer: After this

Re: [Bug 1745648] Re: netplan renders bond lacp-rate as a timevalue should be "fast" or "slow"

You're right. It looks like the unittest passes because it switched to a string which is passed through. But the value of 10 in the tests/generate.py for lacp-rate isn't right and looks like parse is not validating the string value. On Fri, Jan 26, 2018 at 11:42 AM, Mathieu Trudel-Lapierre <

[Bug 1745648] [NEW] netplan renders bond lacp-rate as a timevalue should be "fast" or "slow"

Public bug reported: 1 $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. $ apt-cache policy nplan nplan: Installed: 0.32 Candidate: 0.32 Version table: *** 0.32 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

[Bug 1743618] Re: sru curtin 20180116 - 17.1-5-gfae8ffb1

** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/336172 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743618 Title: sru curtin 2018-01-16 -

[Bug 1743618] Re: sru curtin 2018-01016 - 17.1-5-gfae8ffb1

** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: -* storage: add 'options' key mount type to specify

[Bug 1743631] Re: Install with virtio disk fails due to unknown serial

when installing with curtin, disks can be specified via the 'path' key or 'serial'. When specifying 'serial', curtin will attempt to locate the target disk by glob;ing in /dev/disk/by-id/*serial* to find the disk that matches the specified serial number. In this instance, the virtio disk was not

[Bug 1743618] [NEW] sru curtin 2018-01016 - 17.1-5-gfae8ffb1

Public bug reported: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * storage: add 'options' key mount type to specify mount parameters

[Bug 1735046] Re: mkfs.btrfs error checking mount status of loop device backing_file

I tested the proposed package and it works as expected. root@t-unsubsidized-piper:~# lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 root@t-unsubsidized-piper:~# uname -r 3.13.0-137-generic First, I confirmed it still fails on 3.12-1ubuntu0.1

[Bug 1742560] [NEW] zfsutils-linux recommends dkms when it's not needed

Public bug reported: 1. $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 2. $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu18 Candidate: 0.6.5.6-0ubuntu18 Version table: *** 0.6.5.6-0ubuntu18 500 500

[Bug 1737592] Re: no zfs module in initramfs

Testing a zfsroot deploy without zfs present, curtin will trigger an install of the full linux-image-generic package during the install deps check. This produces this output: [7.696444] cloud-init[1214]: Cloud-init v. 17.1 running 'modules:config' at Thu, 21 Dec 2017 21:39:54 +. Up 6.72

[Bug 1735046] Re: mkfs.btrfs error checking mount status of loop device backing_file

** Description changed: + SRU Template + + [Impact] + + * Users may be unable to successfully create a btrfs filesystem on +block devices when a loop device is mounted and the backing file +no longer exists. This typically happens in the precense of +overlayroot but may be

[Bug 1737817] [NEW] artful bcache NULL pointer defererence

Public bug reported: [ 20.935396] BUG: unable to handle kernel NULL pointer dereference at 0b84 [ 20.936130] IP: _raw_spin_lock_irqsave+0x22/0x40 [ 20.936540] PGD 0 [ 20.936540] P4D 0 [ 20.936725] [ 20.937117] Oops: 0002 [#1] SMP [ 20.937570] Modules linked in:

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

On Tue, Dec 12, 2017 at 5:52 AM, Dimitri John Ledkov wrote: > Once the kernel is fixed, are there any changes that are required to > systemd/udev? > No changes needed. > > ** Changed in: systemd (Ubuntu Bionic) >Status: New => Incomplete > > -- > You received

Re: [Bug 1722311] Re: softlockups/rcu sched

On Tue, Oct 10, 2017 at 2:30 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > Around, September this year is when we started noticing

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Confirmed bionic works as expected. I suspect you can send that upstream with my SoB faster than I can. Definitely interested in seeing if they'll take something like that. On Thu, Dec 7, 2017 at 1:21 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Thanks for testing and the

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Tested the xenial update. I had one boot where the links didn't get created, but I cannot recreate that issue now. On Thu, Dec 7, 2017 at 9:56 AM, Ryan Harper <ryan.har...@canonical.com> wrote: > Here's the Zesty test; all looks good. > > ubuntu@ubuntu:~$ cat /etc/cloud/build.in

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Here's the Zesty test; all looks good. ubuntu@ubuntu:~$ cat /etc/cloud/build.info build_name: server serial: 20171207 ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.10.0-40-generic #44~lp1729145 SMP Wed Dec 6 16:21:45 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ tree /dev/bcache /dev/bcache

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Thanks for doing the cleanup; Patch looks good and I approve. Signed-off-by: Ryan Harper <ryan.har...@canonical.com> On Tue, Dec 5, 2017 at 4:59 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > In the final patch we submit for SRU, it will also include your Sign

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

333685 -> ../../bcache2 ├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0 ├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache3 └── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache1 2 directories, 6 files On Tue, Dec 5, 2017 at 4:00 PM, Ryan Harper <ryan.har...

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Thanks! I'll give it a try today. On Tue, Dec 5, 2017 at 3:43 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > I built an Artful test kernel with the path provided by Ryan. The test > kernel can be downloaded from: > > http://kernel.ubuntu.com/~jsalisbury/lp1729145/ > > Can

[Bug 1736556] Re: mount can exit (success) when it fails

Can you attach: blkid output ls -al /dev/disk/by-label /proc/mounts Testing locally on Xenial, and mount always says something isn't found. % tail -n1 /etc/fstab LABEL=METADATA /mnt vfatdefaults, 0 0 (foudres) ~ % sudo mount -l - /mnt mount: can't find LABEL=METADATA strace

Re: [Bug 1711203] Re: Deployments fail when Secure Boot enabled

Reviewing @slangasek's notes > It's worth checking whether this problem > mysteriously resolves once linux-signed is being pulled in; if it does, > then it's possible we have a bug in grub (enforcing signature when it's > not supposed to) or simply a bug in firmware. It would appear that despite

[Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Revised patch, should fix error with kfree on env ** Patch added: "bcache_always_emit_backing_dev_change_uevent_v2.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5018329/+files/bcache_always_emit_backing_dev_change_uevent_v2.diff -- You received this bug

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Looks like those two kfree's in dev_run can be dropped since that was an exit after kmalloc'ing env entries which are now only done in bch_cached_dev_emit_change() which is only called by dev_run after it knows that the device is not yet running. On Mon, Dec 4, 2017 at 11:35 AM, Ryan Harper

Re: [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

Hi Joseph, Sorry, I didn't give that a compile either; I just wanted to show what the change could look like; Let me see if I can get that to at least compile. On Mon, Dec 4, 2017 at 11:18 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > It looks like env[] was declared in

[Bug 1735821] [NEW] netplan needs bridge port-priority support

Public bug reported: Now that systemd supports port-priority for bridges (LP: #1668347) netplan should handle port-priority like it does path-cost. 1) % lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 1) # lsb_release -rd Description:Ubuntu Bionic Beaver

[Bug 1735821] Re: netplan needs bridge port-priority support

Partial patch; implements networkd side, needs NetworkManager portion and additional unit and integration tests. ** Patch added: "add_bridge_port_priority.patch" https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735821/+attachment/5017168/+files/add_bridge_port_priority.patch -- You

<    3   4   5   6   7   8   9   10   11   12   >