[Bug 1761240] Re: SRU pollinate 4.31

[Ryan Harper]

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) 
GNU/Linux/4.15.0-13-generic/x86_64 Intel(R)/Core(TM)/i7-7500U/CPU/@/2.70GHz 
uptime/163860.00/163784.00 virt/lxc img/serial/20180406

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761240

Title:
  SRU pollinate 4.31

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1761240/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762881

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1762881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 artful-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 234-2ubuntu12.1 500
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
 234-2ubuntu12 500
500 http://azure.archive.ubuntu.com/ubuntu artful/main amd64 Packages


ubuntu@foufoune:~$ time ping  __cloud_init_expected_not_found
ping: __cloud_init_expected_not_found: Temporary failure in name resolution

real0m15.016s
user0m0.000s
sys 0m0.003s

After applying the workaround from comment #11, I see fast lookups
again.

ubuntu@foufoune:~$ cat /etc/systemd/resolved.conf 
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=yes
#MulticastDNS=yes
#DNSSEC=no
#Cache=yes
#DNSStubListener=udp
LLMNR=no

ubuntu@foufoune:~$ time ping  __cloud_init_expected_not_found
ping: __cloud_init_expected_not_found: Name or service not known

real0m0.006s
user0m0.000s
sys 0m0.001s

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
   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/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759664

Title:
  sru curtin 2018-03-28 - 18.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 /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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -
root@ubuntu:~# dpkg --list | grep virtual
ii  linux-headers-virtual  4.13.0.38.41 
amd64Virtual Linux kernel headers
ii  linux-image-virtual4.13.0.38.41 
amd64Virtual Linux kernel image
ii  linux-virtual  4.13.0.38.41 
amd64Minimal Generic Linux kernel and headers
ii  open-vm-tools  2:10.1.10-3ubuntu0.1 
amd64Open VMware Tools for virtual machines hosted on 
VMware (CLI)
root@ubuntu:~# apt update && apt install linux-image-virtual 
Hit:1 http://archive.ubuntu.com/ubuntu artful InRelease
Hit:2 http://security.ubuntu.com/ubuntu artful-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu artful-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu artful-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu artful-proposed InRelease [235 kB]
Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 
[62.3 kB]
Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main Translation-en 
[26.1 kB]
Fetched 323 kB in 1s (206 kB/s)   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
29 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  grub-pc-bin
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic linux-headers-generic 
linux-headers-virtual linux-image-4.13.0-39-generic
  linux-virtual
Suggested packages:
  fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools
The following NEW packages will be installed:
  linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic 
linux-image-4.13.0-39-generic
The following packages will be upgraded:
  linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual
4 upgraded, 3 newly installed, 0 to remove and 25 not upgraded.
Need to get 32.5 MB of archives.
After this operation, 156 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-4.13.0-39 all 4.13.0-39.44 [10.9 MB]
Get:2 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-4.13.0-39-generic amd64 4.13.0-39.44 [704 kB]
Get:3 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-image-4.13.0-39-generic amd64 4.13.0-39.44 [20.9 MB]
Get:4 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-virtual 
amd64 4.13.0.39.42 [1780 B]
Get:5 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-image-virtual amd64 4.13.0.39.42 [2308 B]
Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-virtual amd64 4.13.0.39.42 [1766 B]
Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
linux-headers-generic amd64 4.13.0.39.42 [2294 B]
Fetched 32.5 MB in 5s (5459 kB/s)
Selecting previously unselected package linux-headers-4.13.0-39.
(Reading database ... 57609 files and directories currently installed.)
Preparing to unpack .../0-linux-headers-4.13.0-39_4.13.0-39.44_all.deb ...
Unpacking linux-headers-4.13.0-39 (4.13.0-39.44) ...
Selecting previously unselected package linux-headers-4.13.0-39-generic.
Preparing to unpack 
.../1-linux-headers-4.13.0-39-generic_4.13.0-39.44_amd64.deb ...
Unpacking linux-headers-4.13.0-39-generic (4.13.0-39.44) ...
Selecting previously unselected package linux-image-4.13.0-39-generic.
Preparing to unpack .../2-linux-image-4.13.0-39-generic_4.13.0-39.44_amd64.deb 
...
Done.
Unpacking linux-image-4.13.0-39-generic (4.13.0-39.44) ...
Preparing to unpack .../3-linux-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-virtual (4.13.0.39.42) over (4.13.0.38.41) ...
Preparing to unpack .../4-linux-image-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-image-virtual (4.13.0.39.42) over (4.13.0.38.41) ...
Preparing to unpack .../5-linux-headers-virtual_4.13.0.39.42_amd64.deb ...
Unpacking linux-headers-virtual 

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

[Ryan Harper]

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 users have wanted more than 10 seconds and
in our use-case; I would run with zero-time out.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1760173
>
> Title:
>   zfs, zpool commands hangs for 10 seconds without a /dev/zfs
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1760173/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760173

Title:
  zfs, zpool commands hangs for 10 seconds without a /dev/zfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1760173/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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), but only if the input yaml included
an accept-ra value set.


On Mon, Apr 9, 2018 at 5:22 PM, Stéphane Graber  wrote:
> I'd like to +1 what cyphermox said, the expected behavior on Ubuntu is
> that if you do receive a RA, you let the kernel configure it.
>
> That's how Ubuntu has been ever since IPv6 support was enabled and I
> personally have about 200 systems that very much rely on this (no
> specific IPv6 configuration, just RA based config).
>
> If you turn off IPv6 on your host, this may or may not affect your
> containers, depending on how you've turned it off (globally at kernel
> level, through the default policy or through the all policy).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1732002
>
> Title:
>   cloud images in lxc get ipv6 address
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 writing the Accept-RA unless we
have a value provided in the yaml.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761240] Re: SRU pollinate 4.31

[Ryan Harper]

** 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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761240

Title:
  SRU pollinate 4.31

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1761240/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761573] Re: Network not configured on bionic

[Ryan Harper]

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?

-- 
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 configured on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761573] Re: Network not configured on bionic

[Ryan Harper]

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 bionic instance with these
parameters:

ip=amused-guinea:BOOTIF ip6=off BOOTIF=01-00-25-90-4c-f0-38

With a default virio nic whose MAC does not match and I see the exact
same output.


I repeated that with a Xenial instance and it fails in the same way; so I 
suspect there's something misconfigured w.r.t the MAC on the boot params; or 
possible since this is hardware, something is going on with the MAC addrs on 
the system with the e1000e nics.


** Bug watch added: Red Hat Bugzilla #1525523
   https://bugzilla.redhat.com/show_bug.cgi?id=1525523

-- 
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 configured on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761573] Re: Network not configured on bionic

[Ryan Harper]

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 configured on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761573] Re: Network not configured on bionic

[Ryan Harper]

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.
https://bugs.launchpad.net/bugs/1761573

Title:
  Network not configured on bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1761573/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:
  
   * zfs/zpool version=28 by default, allow users to override default values.
     (LP: #1754013)
   * clear_holders: wipe complex devices before disassembly (LP: #1750519)
   * Add support for installing sources that are a filesystem image.
     (LP: #1746348)
   * clear-holders: detect and remove devices from kernel swap as needed.
     (LP: #1743643)
-  * Add zpool, zfs storage commands for experimental support of ZFS on root.
+  * Add zpool, zfs storage commands for experimental support of ZFS on root.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CurtinUpdates
  
  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html
  
  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed.  A successful run will be required before the proposed curtin
  can be let into -updates.
  
  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug.  Curtin team members will not
  mark ‘verification-done’ until this has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  curtin-proposed test artifacts:
-  * TODO: xenial
-  * TODO: artful
+  * see attached: curtin-vmtest-proposed-x-artifacts.tar.xz
+  * see attached: curtin-vmtest-proposed-a-artifacts.tar.xz
  
  maas-proposed test artifacts (LTS only):
   * TODO: xenial
  
  [Discussion]
  
  == End SRU Template ==
  
  Full Changelog of upstream is below.
  
   - Release 18.1
   - zfs/zpool version=28 by default, allow users to override default values.
     (LP: #1754013)
   - helpers/shell-archive: drop use of tar --sparse flag (LP: #1757565)
   - vmtest: In Basic install, add entry for swap to fstab and verify its use.
   - vmtest: skip some bcache tests pending kernel fixes
   - vmtests: extend skip_by_date for lvmroot_xfsroot and network_mtu
   - vmtest: fix pollinate re.search to use groupdict()
   - Add pollinate user-agent configuration support.
   - vmtest: Remove xenial and trusty specific workaround for rooturl.
   - vmtest: Add Filesystem Battery test.
   - Remove grub2/xenial specific workarounds for zfsroot.
   - Disable dirty_disks mode for mdadm + iscsi tests
   - tools/curtainer: Try harder to get source at binary version.
   - clear_holders: wipe complex devices before disassembly (LP: #1750519)
   - vmtests: network_mtu: fix bug number and move date out one month
   - fix /usr/bin/curtin exit code in install failure (LP: #1751176)
   - docs: Document use of format command with fstype: zfsroot
   - docs: Add HACKING.rst doc to top level dir and readthedocs.
   - vmtest: fix centos root-tgz image sync
   - block_meta: Ensure offset input to sgdisk are integers.
   - Fix error in url_helper and vmtest from previous commit.
   - tools: fix curtainer to specify source version to apt-get source.
   - Add support for installing sources that are a filesystem image.
     (LP: #1746348)
   - clear-holders: detect and remove devices from kernel swap as needed.
     (LP: #1743643)
   - tests: remove xfs filesystem from basic uefi test.
   - tools: fix curtainer --source with trusty.
   - apply_net: do not write to stderr directly.
   - vmtest: Drop use of root-image.gz and maas2roottar.
   - in-target: use ChrootableTarget so that unshare pid is used.
   - tools/curtainer: check that binary and source version are the same.
     (LP: #1747077)
   - Add zfsroot as a filesystem type
   - fix modeline for shell syntax files.
   - error logs: Create error_tarfile path if path does not exist
     (LP: #1746363)
   - zfs: only load zfs on xenial+ skip artful/bionic zfs env export
   - error logs: automatically collect and tar curtin logs upon error.
   - vmtests: Support skipping skip_by_date tests based on environment.
   - Add zpool, zfs storage commands for experimental support of ZFS on root.
   - tests: revert workaround for bug in overlayroot that is now fixed.
   - tests: Bump skip_by_dates for bug 1652822 and 1671952.
   - cli: add curtin collect-logs sub-command
   - vmtest: Do not run tests of unsupported Ubuntu releases.
   - Make license headers and file footers 

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

[Ryan Harper]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759664

Title:
  sru curtin 2018-03-28 - 18.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1759664

Title:
  sru curtin 2018-03-28 - 18.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1759664

Title:
  sru curtin 2018-03-28 - 18.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1759664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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.
https://bugs.launchpad.net/bugs/1761294

Title:
  Network configuration doesn't survive reboots after bionic dist-
  upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 details on how you provided cloud-init configuration in
the desktop scenario.

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760776

Title:
  cloud-init (18.2-0ubuntu1) service is not running in
  ubuntu-18.04-desktop-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

> 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 image customization given a Datasource
with configuration.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760776

Title:
  cloud-init (18.2-0ubuntu1) service is not running in
  ubuntu-18.04-desktop-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 
> installed on a VMware VM.
> Server: http://cdimage.ubuntu.com/ubuntu-server/daily/current/
>
> I did not manually configure /etc/cloud/cloud.cfg either on that Ubuntu
> Server, unfortunately the Server VM has been deleted. I will install a
> new one.
>
> I think ds-identify should be able to find the correct ds on a VMware
> VM, if not true, what's configure should be set here?

cloud-init is looking for a datasource; Did you attach an OVF?
Or an iso with cloud-init user-data?

You're attached ds-identify log shows it found it was running on VMware
but that there were no datasources[1]

VMware typically uses the DatasourceOVF[2], which can be provided to
an image through different transports.

1. http://cloudinit.readthedocs.io/en/latest/topics/datasources.html
2. https://git.launchpad.net/cloud-init/tree/doc/sources/ovf/README

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760776

Title:
  cloud-init (18.2-0ubuntu1) service is not running in
  ubuntu-18.04-desktop-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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: #1755762)
>
>   * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
> - i40e: Fix memory leak related filter programming status
> - i40e: Add programming descriptors to cleaned_count
>
>   * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
> - platform/x86: ideapad-laptop: Increase timeout to wait for EC answer
>
>   * fails to dump with latest kpti fixes (LP: #1750021)
> - kdump: write correct address of mem_section into vmcoreinfo
>
>   * headset mic can't be detected on two Dell machines (LP: #1748807)
> - ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
> - ALSA: hda - Fix headset mic detection problem for two Dell machines
> - ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines
>
>   * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
> - CIFS: make IPC a regular tcon
> - CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
> - CIFS: dump IPC tcon in debug proc file
>
>   * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
> - i2c: octeon: Prevent error message on bus error
>
>   * hisi_sas: Add disk LED support (LP: #1752695)
> - scsi: hisi_sas: directly attached disk LED feature for v2 hw
>
>   * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
> entries with KNL SNC2/SNC4 mode) (LP: #1743856)
> - EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode
>
>   * [regression] Colour banding and artefacts appear system-wide on an Asus
> Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
> - drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
>
>   * DVB Card with SAA7146 chipset not working (LP: #1742316)
> - vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems
>
>   * [Asus UX360UA] battery status in unity-panel is not changing when battery 
> is
> being charged (LP: #1661876) // AC adapter status not detected on Asus
> ZenBook UX410UAK (LP: #1745032)
> - ACPI / battery: Add quirk for Asus UX360UA and UX410UAK
>
>   * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
> - ACPI / battery: Add quirk for Asus GL502VSK and UX305LA
>
>   * support thunderx2 vendor pmu events (LP: #1747523)
> - perf pmu: Extract function to get JSON alias map
> - perf pmu: Pass pmu as a parameter to get_cpuid_str()
> - perf tools arm64: Add support for get_cpuid_str function.
> - perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
> - perf vendor events arm64: Add ThunderX2 implementation defined pmu core
>   events
> - perf pmu: Add check for valid cpuid in perf_pmu__find_map()
>
>   * lpfc.ko module doesn't work (LP: #1746970)
> - scsi: lpfc: Fix loop mode target discovery
>
>   * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
> - powerpc/mm/book3s64: Make KERN_IO_START a variable
> - powerpc/mm/slb: Move comment next to the code it's referring to
> - powerpc/mm/hash64: Make vmalloc 56T on hash
>
>   * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
> - net: hns: add ACPI mode support for ethtool -p
>
>   * CVE-2017-17807
> - KEYS: add missing permission check for request_key() destination
>
>   * [Artful SRU] Fix capsule update regression (LP: #1746019)
> - efi/capsule-loader: Reinstate virtual capsule mapping
>
>   * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
> - Ubuntu: [Config] enable EDAC_GHES for ARM64
>
>   * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
> - SAUCE: tools -- add ability to disable libbfd
> - [Packaging] correct disablement of libbfd
>
>   * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
> - delayacct: Account blkio completion on the correct task
>
>   * Error in CPU frequency reporting when nominal and min pstates are same
> (cpufreq) (LP: #1746174)
> - cpufreq: powernv: Dont assume distinct pstate values for nominal and 
> pmin
>
>   * retpoline abi files are empty on i386 (LP: #1751021)
> - [Packaging] retpoline-extract -- instantiate retpoline files for i386
> - [Packaging] final-checks -- sanity checking ABI contents
> - [Packaging] final-checks -- check for empty retpoline files
>
>   * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when 
> grouping
> different pmu events using perf fuzzer . (perf:) (LP: #1746225)
> - powerpc/perf: Fix oops when grouping different pmu events
>
>   * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
> CVE-2018-126
> - net: create skb_gso_validate_mac_len()
> - bnx2x: 

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

[Ryan Harper]

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.
https://bugs.launchpad.net/bugs/1760776

Title:
  cloud-init (18.2-0ubuntu1) service is not running in
  ubuntu-18.04-desktop-64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1760776/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status

3. When inside a lxd container with zfs storage, zfs list or zpool
status either return or report what's going on.

4. When inside a lxd container with zfs storage, zfs list or zpool
status appears to hang, no output for 10 seconds.

strace reveals that without a /dev/zfs the tools wait for it to appear
for 10 seconds but do not provide a command line switch to disable or
make it more verbose.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: zfsutils-linux 0.6.5.6-0ubuntu19
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Mar 30 18:09:29 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760173

Title:
  zfs, zpool commands hangs for 10 seconds without a /dev/zfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1760173/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 16.03-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3. landscape-client ping caches DNS lookup to canonical.landscape.com,
maybe invalidate cache if ping fails.

4. each ping operation, by default every 30 seconds, looks up v4 and v6
addresses for landscape.canonical.com in-case the IP has changed since
30 seconds ago.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: landscape-client 16.03-0ubuntu2.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Mar 26 18:30:16 2018
InstallationDate: Installed on 2015-05-10 (1051 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: landscape-client
UpgradeStatus: Upgraded to xenial on 2016-09-28 (544 days ago)

** Affects: landscape-client (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759080

Title:
  landscape-client generates dns queries for every ping operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1759080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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; md5sum /usr/bin/python3.6; mkdir 
-p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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.
https://bugs.launchpad.net/bugs/1757565

Title:
  btrfs and tar sparse truncate archives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

v4.15-rc4: GOOD

root@ubuntu:~# uname -r
4.15.0-041500rc4-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

v4.15-rc3: GOOD

root@ubuntu:~# uname -r
4.15.0-041500rc3-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

v4.14-rc2: GOOD

root@ubuntu:~# uname -r
4.15.0-041500rc2-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

So, somewhere between rc1 and rc2.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 remains between tar and btrfs.

Outside of curtin's use of it it, any users of btrfs with any "sparse"
file detection are
vulnerable.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1757565
>
> Title:
>   btrfs and tar sparse truncate archives
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 /usr/bin/python3.6; mkdir 
-p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -


v4.14 Final:  BAD

root@ubuntu:~# uname -r
4.14.0-041400-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -


v4.15-rc1: BAD

root@ubuntu:~# uname -r
4.15.0-041500rc1-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -


Bionic v4.15.0-12-generic: GOOD
root@ubuntu:~# uname -r
4.15.0-12-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 -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf 
/mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
100 /var/lib/dpkg/status
 4.13.0.16.17 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

3. Taring files into an archive are not truncated
4. Files included in tar are filled with NULLs

To reproduce, run an Artful system with one spare disk:

- mkfs.btrfs -f /dev/sda
- mount /dev/sda /mnt
- grep sda /proc/mounts 
/dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

Then run this script which copies a 4MB binary to a btrfs filesystem,
tars the directory up containing the binary; then untars to stdout and
md5sum compares, showing it's different.

% SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
0ce8c4139740198926273853defcb12a  -

And now without the sparse flag:

# SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp 
-a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; 
tar $SPARSE -xzf /mnt/test.tgz -O | md5sum 
e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
e4121d2f3126b8c364bfa1aaa82371a3  -


This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

References:

https://patchwork.kernel.org/patch/10151037/ 
https://www.spinics.net/lists/linux-btrfs/msg56768.html 
https://www.spinics.net/lists/linux-btrfs/msg57111.html

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-virtual 4.13.0.37.40
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
 crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Wed Mar 21 23:08:05 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-37-generic N/A
 linux-backports-modules-4.13.0-37-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful curtin uec-images

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732002

Title:
  cloud images in lxc get ipv6 address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 a boolean parameter. If true, RAs are accepted; if
false, RAs are ignored, independently of the local forwarding state.
When not set, the kernel default is used, and RAs are accepted only when
local forwarding is disabled for that interface. When RAs are accepted,
they may trigger the start of the DHCPv6 client if the relevant flags
are set in the RA data, or if no routers are found on the link.

While in netplan, we've only a boolean, which could be fine, except
netplan defaults to AcceptRA=True which means we have no way of allowing
the kernel configuration to work.

Netplan needs to know if the yaml includes an accept-ra key, and if so,
uses the value set (off or on); but if the yaml does not specify an
accept-ra key, it should *NOT* render a default value.

This allows hosts to defer the the kernel settings.  This key was
introduced as away to resolve a bug where "unconfigured" interfaces got
an IPV6 address due to kernel setting and an IPV6 router present.

https://bugs.launchpad.net/maas/+bug/1655440

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
systemd:
  Installed: 229-4ubuntu21.1
  Candidate: 229-4ubuntu21.1
  Version table:
 *** 229-4ubuntu21.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
root@ubuntu:~# apt-cache policy chrony
chrony:
  Installed: 2.1.1-1
  Candidate: 2.1.1-1
  Version table:
 *** 2.1.1-1 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

3. installing chrony should stop systemd-timesyncd so they both don't
try to adjust time

4. after chrony is installed both systemd-timesyncd and chronyd are
running.

root@ubuntu:~# ps aux | egrep "(chrony|timesync)"
systemd+  1086  0.0  0.2 100324  2368 ?Ssl  19:34   0:00 
/lib/systemd/systemd-timesyncd
_chrony   2770  0.0  0.2 105780  2920 ?S19:38   0:00 
/usr/sbin/chronyd
root  3077  0.0  0.0  12944   924 pts/0S+   19:52   0:00 grep -E 
--color=auto (chrony|timesync)


Note, on bionic the chrony package successfully stops systemd-timesyncd and 
only chronyd remains running after install.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chrony 2.1.1-1
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Mar 19 19:51:06 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: chrony
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chrony (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: chrony (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: chrony (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Affects: chrony (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released


** Tags: amd64 apport-bug uec-images xenial

** Also affects: chrony (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: chrony (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: chrony (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: chrony (Ubuntu Bionic)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756987

Title:
  chrony install does not stop systemd-timesyncd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1756987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
linux-image-virtual:
  Installed: 4.4.0.117.123
  Candidate: 4.4.0.117.123
  Version table:
 *** 4.4.0.117.123 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.4.0.116.122 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 4.4.0.21.22 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
root@ubuntu:~# ls -al /dev/bcache/*
/dev/bcache/by-label:
total 0
drwxr-xr-x 2 root root 120 Mar 19 19:07 .
drwxr-xr-x 4 root root  80 Mar 19 19:07 ..
lrwxrwxrwx 1 root root  13 Mar 19 19:07 backing-sdb -> ../../bcache0
lrwxrwxrwx 1 root root  13 Mar 19 19:07 backing-sdd -> ../../bcache3
lrwxrwxrwx 1 root root  13 Mar 19 19:07 backing-sde -> ../../bcache2
lrwxrwxrwx 1 root root  13 Mar 19 19:07 backing-sdf -> ../../bcache1

/dev/bcache/by-uuid:
total 0
drwxr-xr-x 2 root root 120 Mar 19 19:07 .
drwxr-xr-x 4 root root  80 Mar 19 19:07 ..
lrwxrwxrwx 1 root root  13 Mar 19 19:07 1f531b44-437f-49cc-b7db-16db6d699c41 -> 
../../bcache1
lrwxrwxrwx 1 root root  13 Mar 19 19:07 31474eb7-687d-4bb7-8c6b-b4efd472e860 -> 
../../bcache0
lrwxrwxrwx 1 root root  13 Mar 19 19:07 3653ce1f-b6aa-43ad-9a91-506530db2d50 -> 
../../bcache3
lrwxrwxrwx 1 root root  13 Mar 19 19:07 94041d44-4bb2-4e4d-8641-21d4ae410595 -> 
../../bcache2
root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdb 
lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdb -> 
../../bcache0
root@ubuntu:~# ls -al /sys/class/block/bcache0/slaves
total 0
drwxr-xr-x 2 root root 0 Mar 19 19:08 .
drwxr-xr-x 8 root root 0 Mar 19 19:07 ..
lrwxrwxrwx 1 root root 0 Mar 19 19:08 sda -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Mar 19 19:08 sdb -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:1/2:0:1:0/block/sdb
root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdd
lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdd -> 
../../bcache3
root@ubuntu:~# ls -al /sys/class/block/bcache3/slaves
total 0
drwxr-xr-x 2 root root 0 Mar 19 19:09 .
drwxr-xr-x 8 root root 0 Mar 19 19:07 ..
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sda -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdd -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:3/2:0:3:0/block/sdd
root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sde
lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sde -> 
../../bcache2
root@ubuntu:~# ls -al /sys/class/block/bcache2/slaves
total 0
drwxr-xr-x 2 root root 0 Mar 19 19:09 .
drwxr-xr-x 8 root root 0 Mar 19 19:07 ..
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdc -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sde -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:4/2:0:4:0/block/sde
root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdf
lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdf -> 
../../bcache1
root@ubuntu:~# ls -al /sys/class/block/bcache1/slaves
total 0
drwxr-xr-x 2 root root 0 Mar 19 19:09 .
drwxr-xr-x 8 root root 0 Mar 19 19:07 ..
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdc -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc
lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdf -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:5/2:0:5:0/block/sdf
root@ubuntu:~# dmesg | grep bcache
[1.271827] bcache: register_bdev() registered backing device sdb
[1.276685] bcache: register_bdev() registered backing device sdf
[1.286218] bcache: bch_journal_replay() journal replay done, 0 keys in 2 
entries, seq 13
[1.309504] bcache: bch_cached_dev_attach() Caching sdb as bcache0 on set 
0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[1.313789] bcache: register_cache() registered cache device sda
[1.365415] bcache: bch_journal_replay() journal replay done, 0 keys in 2 
entries, seq 13
[1.380090] bcache: bch_cached_dev_attach() Caching sdf as bcache1 on set 
d36b419d-a49d-42e2-95af-710138a20700
[1.382049] bcache: register_cache() registered cache device sdc
[1.383332] bcache: register_bdev() registered backing device sde
[1.391625] bcache: bch_cached_dev_attach() Caching sde as bcache2 on set 
d36b419d-a49d-42e2-95af-710138a20700
[1.395701] bcache: register_bdev() registered backing device sdd
[1.405870] bcache: bch_cached_dev_attach() Caching sdd as bcache3 on set 
0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[4.533291] bcache: 

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

[Ryan Harper]

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
linux-image-virtual:
  Installed: 4.13.0.38.41
  Candidate: 4.13.0.38.41
  Version table:
 *** 4.13.0.38.41 500
500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.13.0.37.40 500
500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
 4.13.0.16.17 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

ubuntu@ubuntu:~$ ls -al /dev/bcache/by-*
/dev/bcache/by-label:
total 0
drwxr-xr-x 2 root root 120 Mar 19 18:32 .
drwxr-xr-x 4 root root  80 Mar 19 18:32 ..
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdb -> ../../bcache1
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdd -> ../../bcache0
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sde -> ../../bcache3
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdf -> ../../bcache2

/dev/bcache/by-uuid:
total 0
drwxr-xr-x 2 root root 120 Mar 19 18:32 .
drwxr-xr-x 4 root root  80 Mar 19 18:32 ..
lrwxrwxrwx 1 root root  13 Mar 19 18:32 1f531b44-437f-49cc-b7db-16db6d699c41 -> 
../../bcache2
lrwxrwxrwx 1 root root  13 Mar 19 18:32 31474eb7-687d-4bb7-8c6b-b4efd472e860 -> 
../../bcache1
lrwxrwxrwx 1 root root  13 Mar 19 18:32 3653ce1f-b6aa-43ad-9a91-506530db2d50 -> 
../../bcache0
lrwxrwxrwx 1 root root  13 Mar 19 18:32 94041d44-4bb2-4e4d-8641-21d4ae410595 -> 
../../bcache3


ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/
total 0
drwxr-xr-x 2 root root 120 Mar 19 18:32 .
drwxr-xr-x 4 root root  80 Mar 19 18:32 ..
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdb -> ../../bcache1
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdd -> ../../bcache0
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sde -> ../../bcache3
lrwxrwxrwx 1 root root  13 Mar 19 18:32 backing-sdf -> ../../bcache2

ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdb 
lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdb -> 
../../bcache1
ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache1/slaves/
total 0
drwxr-xr-x 2 root root 0 Mar 19 18:36 .
drwxr-xr-x 8 root root 0 Mar 19 18:36 ..
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sda -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdb -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:1/2:0:1:0/block/sdb
ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdd
lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdd -> 
../../bcache0
ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache0/slaves/
total 0
drwxr-xr-x 2 root root 0 Mar 19 18:36 .
drwxr-xr-x 8 root root 0 Mar 19 18:36 ..
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sda -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdd -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:3/2:0:3:0/block/sdd
ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sde
lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sde -> 
../../bcache3
ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache3/slaves/
total 0
drwxr-xr-x 2 root root 0 Mar 19 18:36 .
drwxr-xr-x 8 root root 0 Mar 19 18:36 ..
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdc -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc
lrwxrwxrwx 1 root root 0 Mar 19 18:36 sde -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:4/2:0:4:0/block/sde
ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdf
lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdf -> 
../../bcache2
ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache2/slaves/
total 0
drwxr-xr-x 2 root root 0 Mar 19 18:37 .
drwxr-xr-x 8 root root 0 Mar 19 18:32 ..
lrwxrwxrwx 1 root root 0 Mar 19 18:37 sdc -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc
lrwxrwxrwx 1 root root 0 Mar 19 18:37 sdf -> 
../../../../pci:00/:00:04.0/virtio1/host2/target2:0:5/2:0:5:0/block/sdf

$ dmesg | grep bcache
[1.210989] bcache: register_bdev() registered backing device sdd
[1.214956] bcache: bch_journal_replay() journal replay done, 0 keys in 2 
entries, seq 9
[1.216142] bcache: register_cache() registered cache device sdc
[1.216436] bcache: register_bdev() registered backing device sdb
[1.220348] bcache: bch_journal_replay() journal replay done, 0 keys in 2 
entries, seq 9
[1.233925] bcache: bch_cached_dev_attach() Caching sdb as bcache1 on set 
0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[1.270172] bcache: bch_cached_dev_attach() Caching sdd as bcache0 on set 
0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[1.272236] bcache: 

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

[Ryan Harper]

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 Bionic Beaver (development branch)"
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ubuntu:~$ apt-cache policy linux-image-virtual
linux-image-virtual:
  Installed: 4.15.0.13.14
  Candidate: 4.15.0.13.14
  Version table:
 *** 4.15.0.13.14 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.15.0.12.13 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ubuntu:~$ ls -al /dev/bcache*
brw-rw 1 root disk 251,   0 Mar 19 18:09 /dev/bcache0
brw-rw 1 root disk 251, 128 Mar 19 18:09 /dev/bcache1
brw-rw 1 root disk 251, 256 Mar 19 18:09 /dev/bcache2
brw-rw 1 root disk 251, 384 Mar 19 18:09 /dev/bcache3
ubuntu@ubuntu:~$ dmesg | grep bcache
[1.005037] bcache: register_bdev() registered backing device sdb
[1.011078] bcache: bch_journal_replay() journal replay done, 0
keys in 1 entries, seq 5
[1.023834] bcache: bch_cached_dev_attach() Caching sdb as bcache0
on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[1.029237] bcache: register_cache() registered cache device sda
[1.029555] bcache: register_bdev() registered backing device sdd
[1.050543] bcache: bch_cached_dev_attach() Caching sdd as bcache1
on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa
[1.052124] bcache: register_bdev() registered backing device sde
[1.054044] bcache: register_bdev() registered backing device sdf
[1.058398] bcache: bch_journal_replay() journal replay done, 0
keys in 1 entries, seq 5
[1.068618] bcache: bch_cached_dev_attach() Caching sdf as bcache3
on set d36b419d-a49d-42e2-95af-710138a20700
[1.070652] bcache: bch_cached_dev_attach() Caching sde as bcache2
on set d36b419d-a49d-42e2-95af-710138a20700
[1.076326] bcache: register_cache() registered cache device sdc
[4.090280] bcache: register_bcache() error /dev/sdc: device
already registered
[4.091070] bcache: register_bcache() error /dev/sdd: device
already registered
[4.094397] bcache: register_bcache() error /dev/sde: device
already registered
[4.095253] bcache: register_bcache() error /dev/sda: device
already registered
[4.103178] bcache: register_bcache() error /dev/sdb: device
already registered
[4.115378] bcache: register_bcache() error /dev/sdf: device
already registered

On Mon, Mar 19, 2018 at 5:56 AM, Stefan Bader
 wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this bug with the
> results. If the problem is solved, change the tag 'verification-needed-
> artful' to 'verification-done-artful'. If the problem still exists,
> change the tag 'verification-needed-artful' to 'verification-failed-
> artful'.
>
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754581] Re: trusty bcache NULL pointer exception

[Ryan Harper]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1754581

Title:
  trusty bcache NULL pointer exception

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 changed.
I can reproduce this on multiple trusty kernels:

3.13.0-101-generic (buildd@lgw01-40) #148-Ubuntu SMP Thu Oct 20
22:08:32 UTC 2016
3.13.0-107-generic (buildd@lcy01-09) #154-Ubuntu SMP Tue Dec 20
09:57:27 UTC 2016
3.13.0-137-generic (buildd@lgw01-amd64-058) #186-Ubuntu SMP Mon Dec 4
19:09:19 UTC 2017
3.13.0-143-generic (buildd@lcy01-amd64-010) #192-Ubuntu SMP Tue Feb 27
10:45:36 UTC 2018

>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.16 kernel[0].

I can confirm that newer kernels do not have this issue:

4.4.0-116-generic (buildd@lcy01-amd64-023) (gcc version 4.8.4 (Ubuntu
4.8.4-2ubuntu1~14.04.4))

Xenial, Artful and Bionic are fine.

>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4
>
> ** Changed in: linux (Ubuntu Trusty)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754581
>
> Title:
>   trusty bcache NULL pointer exception
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754581/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754581

Title:
  trusty bcache NULL pointer exception

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754581/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 be removed
/sys/fs/bcache/7834b3df-d029-49a3-9c1b-3fd628db10f2 has been removed
[   70.788038] BUG: unable to handle kernel NULL pointer dereference at 
0a00
[   70.789098] IP: [] journal_write_unlocked+0x130/0x570 
[bcache]
[   70.790167] PGD 8dfa0067 PUD dfb2067 PMD 0 
[   70.790831] Oops:  [#1] SMP 
[   70.791314] Modules linked in: bcache ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr dm_crypt kvm_intel kvm ppdev serio_raw parport_pc 
parport mac_hid i2c_piix4 overlayfs squashfs iscsi_ibft iscsi_boot_sysfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear psmouse virtio_scsi floppy pata_acpi
[   70.792016] CPU: 0 PID: 10996 Comm: kworker/0:3 Not tainted 
3.13.0-142-generic #191-Ubuntu
[   70.792016] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   70.792016] Workqueue: events journal_write_work [bcache]
[   70.792016] task: 88000df76000 ti: 88003a14c000 task.ti: 
88003a14c000
[   70.792016] RIP: 0010:[]  [] 
journal_write_unlocked+0x130/0x570 [bcache]
[   70.792016] RSP: :88003a14dd88  EFLAGS: 00010202
[   70.792016] RAX:  RBX: 88003bf4cba0 RCX: 
[   70.792016] RDX: 88003bf40c48 RSI: 88003bf4cad8 RDI: 88003bec8040
[   70.792016] RBP: 88003a14dde0 R08: 2000efd32f40 R09: 5e80
[   70.792016] R10: dffe982d0cb4cbd0 R11: 0005 R12: 0031
[   70.792016] R13: 88003bf4ccc8 R14: 0001 R15: 88003bf4
[   70.792016] FS:  () GS:88003e20() 
knlGS:
[   70.792016] CS:  0010 DS:  ES:  CR0: 8005003b
[   70.792016] CR2: 0a00 CR3: 3a1ae000 CR4: 0670
[   70.792016] Stack:
[   70.792016]  88003a14ddb0 88003bf4 88003a14dde8 
81013558
[   70.792016]  0df71868 88000df764e8 88003bf4 
88003bf4cba0
[   70.792016]  88003e217300  88003bf4cbd0 
88003a14de00
[   70.792016] Call Trace:
[   70.792016]  [] ? __switch_to+0xe8/0x4f0
[   70.792016]  [] journal_try_write+0x50/0x60 [bcache]
[   70.792016]  [] journal_write_work+0x22/0x30 [bcache]
[   70.792016]  [] process_one_work+0x178/0x470
[   70.792016]  [] worker_thread+0x121/0x410
[   70.792016]  [] ? rescuer_thread+0x430/0x430
[   70.792016]  [] kthread+0xc9/0xe0
[   70.792016]  [] ? kthread_create_on_node+0x1c0/0x1c0
[   70.792016]  [] ret_from_fork+0x58/0x90
[   70.792016]  [] ? kthread_create_on_node+0x1c0/0x1c0
[   70.792016] Code: 10 00 00 00 e8 a2 7a 10 e1 31 c0 66 83 bb 94 38 ff ff 00 
48 8b 8b a0 40 ff ff 49 8d 97 48 0c 00 00 74 3b 0f 1f 84 00 00 00 00 00 <48> 8b 
b9 00 0a 00 00 0f b7 89 ce 00 00 00 83 c0 01 49 8b 75 00 
[   70.792016] RIP  [] journal_write_unlocked+0x130/0x570 
[bcache]
[   70.792016]  RSP 
[   70.792016] CR2: 0a00
[   70.792016] ---[ end trace c5387a4b27c41667 ]---
Running command ['udevadm', 'settle'] with allowed return codes [0] 
(capture=False)
[   70.831831] BUG: unable to handle kernel paging request at ffd8
[   70.832822] IP: [] kthread_data+0x10/0x20
[   70.833396] PGD 1c13067 PUD 1c15067 PMD 0 
[   70.833396] Oops:  [#2] SMP 
[   70.833396] Modules linked in: bcache ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr dm_crypt kvm_intel kvm ppdev serio_raw parport_pc 
parport mac_hid i2c_piix4 overlayfs squashfs iscsi_ibft iscsi_boot_sysfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 
async_memcpy async_raid6_recov async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear psmouse virtio_scsi floppy pata_acpi
[   70.833396] CPU: 0 PID: 10996 Comm: kworker/0:3 Tainted: G  D   
3.13.0-142-generic #191-Ubuntu
[   70.833396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
[   70.833396] task: 88000df76000 ti: 88003a14c000 task.ti: 
88003a14c000
[   70.833396] RIP: 0010:[]  [] 
kthread_data+0x10/0x20
[   70.833396] RSP: 0018:88003a14d9c0  EFLAGS: 00010002
[   70.833396] RAX:  RBX:  RCX: 000f
[   70.833396] RDX: 0003 RSI:  RDI: 88000df76000
[   70.833396] RBP: 88003a14d9c0 R08:  R09: 88003e216f20
[   70.833396] R10: 8106887c R11: ea357200 R12: 88003e213b00
[   70.833396] R13:  R14: 88000df75ff0 R15: 88000df76000
[   70.833396] FS:  () GS:88003e20() 

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

[Ryan Harper]

** 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:
  mdadm-last-resort@.service runs when array is active

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1753786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753786

Title:
  mdadm-last-resort@.service runs when array is active

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1753786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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. ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

2. ubuntu@ubuntu:~$ apt-cache policy mdadm
mdadm:
  Installed: 4.0-2
  Candidate: 4.0-2
  Version table:
 *** 4.0-2 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
3. /dev/md0 stays mounted after boot
4. /dev/md0 is unmounted from the system due to mdadm-last-resort@md0.service 
running

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mdadm 4.0-2 [modified: lib/systemd/system/mdadm-last-resort@.service]
ProcVersionSignature: User Name 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Mar  6 16:03:25 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed 
with exit code 1: mdadm: cannot open /dev/sda: Permission denied
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed 
with exit code 1: mdadm: cannot open /dev/sdb: Permission denied
MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed 
with exit code 1: mdadm: cannot open /dev/sdc: Permission denied
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=413f8b88-2156-11e8-93a3-525400123400 ro console=ttyS0
ProcMDstat:
 Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10] 
 md0 : active raid5 sdc[1] sdb[0] sda[3]
   10477568 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
   
 unused devices: 
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-bionic
dmi.sys.vendor: QEMU
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
mdadm.conf:
 ARRAY /dev/md0 metadata=1.2 spares=1 name=ubuntu:0 
UUID=aefcb03c:f7588463:d51ac0c1:3dfa8d62
 MAILADDR root

** Affects: mdadm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful curtin uec-images

-- 
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:
  mdadm-last-resort@.service runs when array is active

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1753786/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
  Version table:
 *** 0.33 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3. netplan generate detects invalid config, in error message reports the
line and column correctly to where the error was found.

4. netplan generate reports an error, but the location isn't accurate.


root@b2:~# cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
mtu: 1501
addresses:
- 2001:4800:78ff:1b:be76:4eff:fe06:96b3/64
bridges:
br0:
addresses: []
accept-ra: true


vlans:
  vlan.45:
 id: 45
 link: eth0

root@b2:~# netplan generate
Error in network definition //etc/netplan/50-cloud-init.yaml line 5 column 0: 
unknown key vlans

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nplan 0.33
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Mar  2 18:51:49 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nplan (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic third-party-packages uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752956

Title:
  netplan generate error message points to the wrong line number

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1752956/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3. netplan configuration creates a bridge with a priority value and matches
the value in /sys/class/net//bridge/priority

4. /sys/class/net//bridge/priority is the default value
32768 despite /etc/netplan/50-cloud-init.yaml specifies a priority value
for the bridge.

--

The networkd renderer silently drops writing of Priority value to the
[Bridge] section in a bridge's .netdev file.

The code says this:

netplan/src/networkd.c:69
#if 0
/* FIXME: Priority= is not valid for the bridge itself, although it should 
work as the
 *STP priority of the bridge itself. It's not supported by 
networkd, but let's
 *keep it around in case it becomes supported in the future.
 */
if (def->bridge_params.priority)
g_string_append_printf(params, "Priority=%u\n", 
def->bridge_params.priority);
#endif

But bridge priority is settable via sysfs (with the bridge down) and via
brctl setbridgeprio

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nplan 0.33
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Tue Feb 27 20:14:24 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nplan (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug bionic third-party-packages uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752162

Title:
  netplan 0.33 silently breaks bridge-priority

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1752162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 systemd-timesyncd where present

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 it has an ipv6 enabled bridge; it could control the
template to use a dhcp6 config instead of dhcp (which is ipv4) and not
the unconfigured IPV6 RA, which on older releases like Xenial and Trusty
won't see without configuration anyhow.

https://code.launchpad.net/~raharper/cloud-init/+git/cloud-
init/+merge/339437

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 use sys.exit();
the collection method (create_log_tarfile) need only return.


 % git diff
diff --git a/curtin/commands/collect_logs.py b/curtin/commands/collect_logs.py
index a61d91e..2078f37 100644
--- a/curtin/commands/collect_logs.py
+++ b/curtin/commands/collect_logs.py
@@ -48,6 +48,7 @@ def collect_logs_main(args):
 SAVE_INSTALL_CONFIG, CURTIN_PACK_CONFIG_DIR))
 cfg = CONFIG_BUILTIN.copy()
 create_log_tarfile(args.output, cfg)
+sys.exit(0)
 
 
 def create_log_tarfile(tarfile, config):
@@ -104,7 +105,7 @@ def create_log_tarfile(tarfile, config):
 if os.path.exists(tmp_dir):
 shutil.rmtree(tmp_dir)
 sys.stderr.write('Wrote: %s\n' % tarfile)
-sys.exit(0)
+return

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: curtin 17.1-37-g82622f12-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Fri Feb 23 02:00:28 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: curtin
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: curtin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751176

Title:
  curtin exit codes broken by collect_logs misuse of sys.exit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1751176/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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: /etc/systemd/network/10-netplan-lo.network
Type: loopback
   State: carrier (configured)
 Address: 127.0.0.1
  ::1
 DNS: 10.90.90.1
  Search Domains: maaslab
  maas

● 38: eth0
   Link File: n/a
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
   State: routable (configured)
  HW Address: 00:16:3e:4c:5b:4b (Xensource, Inc.)
 Address: 10.8.107.71
  fe80::216:3eff:fe4c:5b4b
 Gateway: 10.8.107.1
 DNS: 10.8.107.1
  Search Domains: lxd
root@b1:~# systemd-resolve --status --no-pager 
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 38 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.8.107.1
  DNS Domain: lxd


networkctl processed the .network file but systemd-resolved didn't seem to 
notice it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750884

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 'After=local-fs.target' essentially pushes cloud-init to have that
> same dependency, which it does not have.  We don't really want cloud-init
> to have to wait for local-fs.target.
> For example see bug 1691489 (and related fallout bug 1717477).
>

I don't think it's so clear that it effectively pushes cloud-init-local out
to after local-fs.target
as, in general, cloud-init-local already runs *after* local-fs.target

Feb 22 15:48:47.065442 b2 systemd[1]: Started Set the console keyboard
layout.
Feb 22 15:48:47.066519 b2 systemd[1]: Reached target Local File Systems
(Pre).
Feb 22 15:48:47.066580 b2 systemd[1]: Reached target Local File Systems.
...
Feb 22 15:48:47.108237 b2 systemd[1]: systemd-tmpfiles-setup.service
...
Feb 22 15:48:47.153217 b2 systemd[1]: Starting Initial cloud-init job
(pre-networking)...

That's in bionic, without open-vm-tools.

I think we need some more information w.r.t open-vm-tools actual
requirement w.r.t running prior to cloud-init;
Assuming there is a need to run before cloud-init-local, then the unit
needs to be as precise as cloud-init
w.r.t what it actually requires w.r.t the filesystem (like the
RequiresMountFor).

IIUC, the bugs were related to blocking fsck and mount service to require
cloud-init.service, but that required local-fs.target
and a loop was created.  Open-vm-tools is asking to run after
cloud-init-local, which is not emitted in any of mount entries
so I don't see  a new loop coming.




>
> If the only reason for local-fs.target was actually PrivateTmp, then there
> is a bug in systemd.
>
> https://www.freedesktop.org/software/systemd/man/systemd.exec.html
>  | Implicit Dependencies
>  | Similar, units with PrivateTmp= enabled automatically get mount unit
>  | dependencies for all mounts required to access /tmp and /var/tmp. They
>  | will also gain an automatic After= dependency on systemd-tmpfiles-
>  | setup.service(8).
>
>  So there must have been a different read-only filesystem involved.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1750780
>
> Title:
>   Race with local file systems can make open-vm-tools fail to start
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750780

Title:
  Race with local file systems can make open-vm-tools fail to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 21, 2018 at 10:46 AM, Andreas Hasenack 
wrote:

> I'm still seeing this in yesterday's (feb 21st) image, fwiw.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743643
>
> Title:
>   Install to dirty disk with swap fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743643/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743643

Title:
  Install to dirty disk with swap fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1743643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 the system is up.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750780

Title:
  Race with local file systems can make open-vm-tools fail to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
> alternative NTP server is to be used.
>

I'm not opposed to having cloud-init do that.  But systemd and ntp clients
are
installable outside of cloud images and they should behave consistently
there.
I think a combination of the override which prevents timesyncd from
starting if a client
is present *and* the Conflicts= that's present in Bionic should be in the
packaging.

Such a configuration would prevent timesyncd starting from stopping other
clients.


> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1749722
>
> Title:
>   NTP: take into account systemd-timesyncd where present
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions
>

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 started. So, if ntp or chrony unit were to start, it would stop
timesyncd.

This is roughly equivalent, however, it does leave timesyncd unit
enabled.  This means that if something starts systemd-timesyncd.service,
it would stop the ntp or chrony service.

There may be additional work on each of the time packages to *disable*
timesyncd unit when installed such that it won't start.  This may not be
possible to prevent users from starting timesyncd manually.

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

@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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 specific
+device could possible be pointing to a different dataset
+altogether.  bcache udev rules do provide some mechanism to
+generate persistent symlinks in /dev/bcache/by-uuid or
+/dev/bcache/by-label which is based on superblock data on
+the underlying device.  However, the Linux kernel does not
+always generate an kernel uevent to trigger the udev rules
+to create the symlink.
+ 
+  * The fix adds a udev program which will read bcache superblock
+of slave devices and extract the UUID and LABEL, exporting them
+to udev for use in the bcache rule files.
+ 
+  * This is affected in upstream bcache-tools, the owning package
+of the udev rules.  This affects all releases of bcache-tools
+as the rules rely upon the kernel to trigger these events,
+though that is not a requirement to resolve the lack of
+persistent links.
+  
+ [Test Case]
+ 
+  * Launch and Ubuntu Cloud Image with 3 unused disks
+- apt install bcache-tools tree
+- make-bcache -C /dev/vdb
+- make-bcache -B /dev/vdc
+- make-bcache -B /dev/vdd
+- echo "vdc" > /sys/class/block/bcache0/bcache/label
+- echo "vdd" > /sys/class/block/bcache1/bcache/label
+- reboot
+ 
+- Run this test:
+ 
+ #!/bin/bash
+ FAIL=0
+ [ ! -d /dev/bcache ] && { 
+ echo "FAIL: /dev/bcache is not a directory";
+ exit 1
+ }
+ for label in /dev/bcache/by-label/*; do
+ LABEL_TARGET="$(ls -1 /sys/class/block/`basename $label`/holders/)"
+ DEVNAME=`readlink -f $label`;
+ KNAME="${DEVNAME#*/dev/}"
+ if [ "$LABEL_TARGET" != "$KNAME" ]; then
+ echo "FAIL: label points to $LABEL_TARGET but symlink points to 
$DEVNAME";
+ FAIL=1
+ fi;
+ done
+ if [ "$FAIL" == "0" ]; then
+ echo "PASS";
+ exit 0
+ fi
+ exit 1
+ 
+  
+ [Regression Potential]
+ 
+  * As bcache minor numbers and these symlinks have been unreliable in
+the past there may be code that makes assumptions about
+/dev/bcache* expanded only to the block devices, versus
+/dev/bcache which is a directory.
+ 
+ 
+ [Original Description]
+ 
  Bcache device names like /dev/bcache0 are unstable.  Bcache does not use
  any predictable ordering when assembling bcache devices, so on systems
  with multiple bcache devices, a symlink to /dev/bcache0 may end up
  pointing do a different device.
  
  the bcache dname symlink should point to the /dev/bcache/by-uuid/
  which matches the backing device UUID that's set at creation time.

-- 
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 dname for bcache uses unstable devname instead of UUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 dname for bcache uses unstable devname instead of UUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728742

Title:
  curtin dname for bcache uses unstable devname instead of UUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 apt policy nplan 
Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:3 http://ppa.launchpad.net/raharper/experimental/ubuntu bionic InRelease
   
Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease 
   
Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease [235 kB]
Hit:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Get:7 http://archive.ubuntu.com/ubuntu bionic/universe Sources [9019 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1010 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8372 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/universe Translation-en [4921 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 
[146 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-proposed/main Translation-en 
[59.8 kB]
Fetched 24.0 MB in 5s (4439 kB/s)   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
45 packages can be upgraded. Run 'apt list --upgradable' to see them.
nplan:
  Installed: 0.32
  Candidate: 0.33
  Version table:
 0.33 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
 *** 0.32 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
root@b2:~# sudo apt install nplan 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  network-manager | wpasupplicant
The following packages will be upgraded:
  nplan
1 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
Need to get 41.6 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 nplan amd64 
0.33 [41.6 kB]
Fetched 41.6 kB in 1s (81.1 kB/s)
(Reading database ... 27026 files and directories currently installed.)
Preparing to unpack .../archives/nplan_0.33_amd64.deb ...
Unpacking nplan (0.33) over (0.32) ...
Setting up nplan (0.33) ...
Processing triggers for man-db (2.8.1-1) ...
root@b2:~# cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
match:
name: 'eth0'

bridges:
br0:
addresses:
- 192.168.14.2/24
interfaces:
- eth0
parameters:
path-cost:
eth0: 50
priority: 22
port-priority:
eth0: 14


root@b2:~# netplan generate
root@b2:~# set -o vi
root@b2:~# cat /run/systemd/network/10-netplan-eth0.network 
[Match]
Name=eth0

[Network]
Bridge=br0
LinkLocalAddressing=no
IPv6AcceptRA=no

[Bridge]
Cost=50
Priority=14

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735821

Title:
  netplan needs bridge port-priority support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 the list are in an operational down state, the 
current link is brought down. When at least one link has carrier, the current 
interface is brought up.

I tested this, and it appears to work:

# cat /run/systemd/network/10-netplan-br0.network 
[Match]
Name=br0

[Network]
BindCarrier=eth1
root@b1:~# networkctl status br0
● 2: br0
   Link File: n/a
Network File: /run/systemd/network/10-netplan-br0.network
Type: ether
   State: degraded (configured)
  HW Address: ee:17:6d:12:fe:c5
 Address: fe80::ec17:6dff:fe12:fec5
Carrier Bound To: eth1

root@b1:~# ip link show br0
2: br0:  mtu 1500 qdisc noqueue state UP mode 
DEFAULT group default qlen 1000
link/ether ee:17:6d:12:fe:c5 brd ff:ff:ff:ff:ff:ff

root@b1:~# ip link show eth1
94: eth1@if95:  mtu 1500 qdisc noqueue master 
br0 state UP mode DEFAULT group default qlen 1000
link/ether 00:16:3e:02:88:ea brd ff:ff:ff:ff:ff:ff link-netnsid 0

However, it's not clear to me that we want to bring down br0 if one or
more of the interfaces were to go down, so this may be something that
needs a better upstream fix.

This issue seemed to match:
https://github.com/systemd/systemd/issues/425

And some users seem to be working around by emitting units which are
effectively a network-online hook, but that doesn't look very clean IMO.

** Bug watch added: github.com/systemd/systemd/issues #425
   https://github.com/systemd/systemd/issues/425

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748332

Title:
  Bridges fail to come online when configured via LXD, netplan, and
  cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1748332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 and cloud-final can
run.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cloud-init 17.2-30-gf7deaf15-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CloudName: NoCloud
Date: Wed Feb  7 17:10:29 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
user_data.txt:
 #cloud-config
 ssh_authorized_keys:
   - ssh-rsa 
B3NzaC1yc2EDAQABAAABAQDeShzUvzOCPWKyfRt0IsiO4//nyDwe6JgL0ZTHO+Wq1nRsuwysdoX9sAMlhAdgx3q6qbJu6Xa3ug1c4rqyszBBovsoOieF4ZzZzrPV4ekzzAaPB5jqCIRostiIimTnxOrnyRtdZ0F81q1jzL9SfyzlzhIVYvdcleEE8c2ziaNZfAeL/cD9MB9jCcxRTNuMQw27QE2yQ4na2YAm3tB0l6vDfiLIx9hstgwyj13I5VsFcoHNohyN0R+Fq6/Zz5rOHiUieiMcs0+b/khnfYKuqygQRpPWAl35OVJUSUgVnbRQsM9TstOfy5IxFxI5oBtueVX1ZUp/xibsZo/1V3dJkKet
 rharper@brettanomyces

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Assignee: Chad Smith (chad.smith)
 Status: New


** Tags: amd64 apport-bug bionic uec-images

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Chad Smith (chad.smith)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747965

Title:
  cloud-init status reports done before boot is finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747965/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

*** 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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747553

Title:
  dhcp allow client-identifier control

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1747553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

*** 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

ClientIdentifier=
The DHCPv4 client identifier to use. Either "mac" to use the MAC address of the 
link or "duid" (the default, see below) to use an RFC4361-compliant Client ID.

** Affects: nplan (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/1747553

Title:
  dhcp allow client-identifier control

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1747553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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:
 *** 17.2-13-g6299e8d0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3. cloud-init status should give me status on if it's running or
finished, etc

4. cloud-init stack traces
(neipa) ~ % lxc launch ubuntu-daily:bionic b2 
Creating b2
Starting b2
(neipa) ~ % lxc exec b2 /bin/bash
root@b2:~# systemctl status
● b2
State: initializing
 Jobs: 62 queued
   Failed: 0 units
Since: Tue 2018-02-06 00:58:41 UTC; 9s ago
   CGroup: /
   ├─123 /bin/bash
   ├─133 systemctl status
   ├─134 pager
   ├─init.scope
   │ └─1 /sbin/init
   └─system.slice
 ├─systemd-networkd-wait-online.service
 │ └─120 /lib/systemd/systemd-networkd-wait-online
 ├─systemd-resolved.service
 │ └─121 /lib/systemd/systemd-resolved
 ├─systemd-udevd.service
 │ └─52 /lib/systemd/systemd-udevd
 ├─systemd-journald.service
 │ └─51 /lib/systemd/systemd-journald
 └─systemd-networkd.service
   └─119 /lib/systemd/systemd-networkd
root@b2:~# set -o vi
root@b2:~# ^Cstemctl status
root@b2:~# cloud-init status
Traceback (most recent call last):
  File "/usr/bin/cloud-init", line 11, in 
load_entry_point('cloud-init==17.2', 'console_scripts', 'cloud-init')()
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 859, in main
get_uptime=True, func=functor, args=(name, args))
  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2279, in 
log_time
ret = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 55, in 
handle_status_args
status, status_detail, time = _get_status_details(init.paths)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 114, in 
_get_status_details
CLOUDINIT_DISABLED_FILE, paths)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 96, in 
_is_cloudinit_disabled
return (is_disabled, reason)
UnboundLocalError: local variable 'reason' referenced before assignment
root@b2:~# cloud-init status

** Affects: cloud-init (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/1747554

Title:
  cloud-init status in bionic stack traces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1747554/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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.
https://bugs.launchpad.net/bugs/1747077

Title:
  curtainer needs to check installed version vs. source version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1747077/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 operation, 18.2 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 binutils amd64 
2.26.1-1ubuntu1~16.04.6 [2311 kB]
Get:2 http://ppa.launchpad.net/curtin-dev/daily/ubuntu xenial/main amd64 
curtin-common all 17.1-575-g6d23a6f-0ubuntu1~ubuntu16.04.1 [11.3 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdpkg-perl 
all 1.18.4ubuntu1.3 [195 kB]
Get:4 http://ppa.launchpad.net/curtin-dev/daily/ubuntu xenial/main amd64 
python3-curtin all 17.1-575-g6d23a6f-0ubuntu1~ubuntu16.04.1 [106 kB]
Get:5 http://archive.ubuntu.com/ubuntu xenial/main amd64 make amd64 4.1-6 [151 
kB]
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 dpkg-dev all 
1.18.4ubuntu1.3 [584 kB]
Get:7 http://ppa.launchpad.net/curtin-dev/daily/ubuntu xenial/main amd64 curtin 
all 17.1-575-g6d23a6f-0ubuntu1~ubuntu16.04.1 [2610 B]
Fetched 3362 kB in 1s (3069 kB/s)

This installs 17.1-575

Notice the source package version:


Need to get 299 kB of source archives.
Get:1 http://ppa.launchpad.net/curtin-dev/daily/ubuntu xenial/main curtin 
17.1-576-g15c15c7-0ubuntu1~ubuntu16.04.1 (tar) [298 kB]
Get:2 http://ppa.launchpad.net/curtin-dev/daily/ubuntu xenial/main curtin 
17.1-576-g15c15c7-0ubuntu1~ubuntu16.04.1 (dsc) [1149 B]
dpkg-source: warning: extracting unsigned source package 
(curtin_17.1-576-g15c15c7-0ubuntu1~ubuntu16.04.1.dsc)
dpkg-source: info: extracting curtin in curtin-17.1-576-g15c15c7
dpkg-source: info: unpacking 
curtin_17.1-576-g15c15c7-0ubuntu1~ubuntu16.04.1.tar.xz

This fetches source 17.1-576

curtainer needs to compare curtin --version with the src/curtin/version.py
and raise an error if there is a mismatch.

Attaching console log

** Affects: curtin (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/1747077

Title:
  curtainer needs to check installed version vs. source version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1747077/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 <
mathieu...@gmail.com> wrote:

> If it's the case, then this would be a critical bug. However, it looks
> to me like LACP rate is being properly handled, values are 'slow' or
> 'fast', and an integration test exists to validate that.
>
> ** Changed in: nplan (Ubuntu)
>Status: New => Triaged
>
> ** Changed in: nplan (Ubuntu)
>Importance: Undecided => Critical
>
> ** Changed in: nplan (Ubuntu)
>  Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
>
> ** Changed in: nplan (Ubuntu)
>Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745648
>
> Title:
>   netplan renders bond lacp-rate as a timevalue should be "fast" or
>   "slow"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/
> 1745648/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745648

Title:
  netplan renders bond lacp-rate as a timevalue should be "fast" or
  "slow"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1745648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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
100 /var/lib/dpkg/status

3. configuring a bond with lacp-rate: fast or slow
4. netplan fails to parse the lacp-rate as a string, expects it to be a time 
value

The systemd-networkd netdev documentation[A] indicates that
LACPTransmitRate (which the netplan lacp-rate key maps to) has two
values:  "fast" and "slow"  but netplan is rendering an integer.

A. https://www.freedesktop.org/software/systemd/man/systemd.netdev.html

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nplan 0.32
ProcVersionSignature: User Name 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
Date: Fri Jan 26 17:28:23 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nplan (Ubuntu)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: Triaged


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745648

Title:
  netplan renders bond lacp-rate as a timevalue should be "fast" or
  "slow"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1745648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 - 17.1-6-g8b145067

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/xenial/+source/curtin/+bug/1743618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

** 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 mount parameters for
-  filesystems (LP# 1709284)
-* Re-add curthooks.write_files method for backwards compat (LP: #1731709)
-* block: handle wiping bcache parts (LP: #1718699)
-* bcache: accept sysfs write failure in shutdown handler if path missing
-  (LP: #1700564)
-* block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
-  tables (LP: #1722322)
+    * storage: add 'options' key mount type to specify mount parameters for
+  filesystems (LP: #1709284)
+    * Re-add curthooks.write_files method for backwards compat
+  (LP: #1731709)
+    * block: handle wiping bcache parts (LP: #1718699)
+    * bcache: accept sysfs write failure in shutdown handler if path
+  missing (LP: #1700564)
+    * block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
+  tables (LP: #1722322)
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CurtinUpdates
  
  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html
  
  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed.  A successful run will be required before the proposed curtin
  can be let into -updates.
  
  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug.  Curtin team members will not
  mark ‘verification-done’ until this has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  
  
  
  [Discussion]
  The primary motiviation for this SRU is to bring 'options' mount parameters 
(LP# 1709284).
  
  == End SRU Template ==
  
  

-- 
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-01016 - 17.1-5-gfae8ffb1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1743618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 provided with a serial number,
probert appears to have provided a serial number of 'Unknown_Serial'
which was not found in /dev/disk/by-id/ on the install source machine.

subiquity likely needs to determine if it can use 'serial' or 'path'
based on the probert information.  Probert may need to omit serial
value, or use a 'none' value instead of 'Unknown_Serial'.

If we're feeling lucky, we could also file a qemu bug to see if upstream
is interested in having virtio disks have a default serial number like
IDE devices do (as well as network devices which get a default mac
address).

** Also affects: curtin
   Importance: Undecided
   Status: New

** Changed in: curtin
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743631

Title:
  Install with virtio disk fails due to unknown serial

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1743631/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 for
 filesystems (LP# 1709284)
   * Re-add curthooks.write_files method for backwards compat (LP: #1731709)
   * block: handle wiping bcache parts (LP: #1718699)
   * bcache: accept sysfs write failure in shutdown handler if path missing
 (LP: #1700564)
   * block_meta: use block.wipe_volume(mode=superblock) to clear MBR/GPT
 tables (LP: #1722322)

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/CurtinUpdates

Curtin now contains an extensive integration test suite that is ran using
the SRU package for each releases. These suite has documentation here:
https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

In order to avoid regression to existing MAAS product, the MAAS team will
run their continuous integration test against the curtin that is in
-proposed.  A successful run will be required before the proposed curtin
can be let into -updates.

The curtin team will be in charge of attaching the artifacts and console
output of the appropriate run to the bug.  Curtin team members will not
mark ‘verification-done’ until this has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.




[Discussion]
The primary motiviation for this SRU is to bring 'options' mount parameters 
(LP# 1709284).

== End SRU Template ==



** Affects: curtin (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/1743618

Title:
  sru curtin 2018-01016 - 17.1-5-gfae8ffb1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1743618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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

root@t-unsubsidized-piper:~# truncate -s 1G testloop.img
root@t-unsubsidized-piper:~# losetup /dev/loop0 testloop.img
root@t-unsubsidized-piper:~# mkfs.ext4 /dev/loop0
mke2fs 1.42.9 (4-Feb-2014)
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

root@t-unsubsidized-piper:~# mount /dev/loop0 /mnt
root@t-unsubsidized-piper:~# rm testloop.img
root@t-unsubsidized-piper:~# mkfs.btrfs --force /dev/vdb
Error: error checking /dev/vdb mount status
root@t-unsubsidized-piper:~# echo $?
1

Next I added trusty-proposed and updated

root@t-unsubsidized-piper:~# apt-cache policy btrfs-tools
btrfs-tools:
  Installed: 3.12-1ubuntu0.1
  Candidate: 3.12-1ubuntu0.2
  Version table:
 3.12-1ubuntu0.2 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-proposed/main 
amd64 Packages
 *** 3.12-1ubuntu0.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 3.12-1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 
Packages

After installing the upgrade, I repeated the mkfs.btrfs command, but
this time it succeeds

# sudo apt install btrfs-tools
sudo: unable to resolve host t-unsubsidized-piper
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  btrfs-tools
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 332 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-proposed/main 
btrfs-tools amd64 3.12-1ubuntu0.2 [332 kB]
Fetched 332 kB in 0s (827 kB/s) 
(Reading database ... 51345 files and directories currently installed.)
Preparing to unpack .../btrfs-tools_3.12-1ubuntu0.2_amd64.deb ...
Unpacking btrfs-tools (3.12-1ubuntu0.2) over (3.12-1ubuntu0.1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up btrfs-tools (3.12-1ubuntu0.2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.103ubuntu4.10) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-137-generic
Processing triggers for libc-bin (2.19-0ubuntu6.13) ...
root@t-unsubsidized-piper:~# mkfs.btrfs --force /dev/vdb

WARNING! - Btrfs v3.12 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using

Turning ON incompat feature 'extref': increased hardlink limit per file to 65536
fs created label (null) on /dev/vdb
nodesize 16384 leafsize 16384 sectorsize 4096 size 40.00GiB
Btrfs v3.12
root@t-unsubsidized-piper:~# echo $?
0


** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735046

Title:
  mkfs.btrfs error checking mount status of loop device backing_file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1735046/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.6.5.6-0ubuntu8 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

3. apt install zfsutils-linux does not install dkms,spl-dkms and
dependencies since 16.04 kernel already contains zfs.ko

4. apt install zfsutils-linux installs all of the following:

dkms fakeroot gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 
libcilkrts5 libfakeroot libfreetype6 libgcc-5-dev libgomp1 libitm1
  liblsan0 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages-dev 
spl spl-dkms

and then any kernel install/update then attempts to dkms rebuild zfs and
spl even though the modules are already provided.

% dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko
linux-image-4.13.0-19-generic: 
/lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko
% dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko
linux-image-4.13.0-19-generic: 
/lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko


We can see from the package requirements, that it Recommends zfs-dkms, but only 
on Xenial.  Releases newer than Xenial do not have this package requirement.  

% apt-cache show zfsutils-linux
Package: zfsutils-linux
Architecture: amd64
Version: 0.6.5.6-0ubuntu18
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Darik Horn 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 779
Provides: zfs
Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu18), 
libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), 
libuutil1linux, libzfs2linux, libzpool2linux, python3:any (>= 3.3.2-2~), python3
Recommends: zfs-dkms, zfs-zed
Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs
Conflicts: zfs, zfs-fuse
Replaces: zfs
Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.6-0ubuntu18_amd64.deb
Size: 275970
MD5sum: 02ead25f1fed812980d70865da916468
SHA1: e6736c223c3b2198bba8777153836bb8d4789518
SHA256: c4ad2b81ee13072cb3f4e31fd3aed93cf66c7c50872fc542cc2425120b222eed
Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6
Description-en: Native OpenZFS management utilities for Linux
 This package provides the zpool and zfs commands that are used to
 manage OpenZFS filesystems.
Description-md5: 7b0f98269f6c33505790717cd478736c
Supported: 5y


Here's Artful
~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache show zfsutils-linux
Package: zfsutils-linux
Architecture: amd64
Version: 0.6.5.11-1ubuntu3
Priority: extra
Section: admin
Source: zfs-linux
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian ZFS on Linux maintainers 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 1100
Provides: zfsutils
Depends: init-system-helpers (>= 1.18~), libblkid1 (>= 2.16), libc6 (>= 2.14), 
libnvpair1linux, libuuid1 (>= 2.16), libuutil1linux, libzfs2linux, 
libzpool2linux, python3:any, python3
Recommends: lsb-base, zfs-zed
Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | 
zfs-dracut
Conflicts: zfs, zfs-fuse, zutils
Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.11-1ubuntu3_amd64.deb
Size: 328574
MD5sum: d1ce7f5ffa75c9b46e7d5285430efff3
SHA1: 8a8ab05186b83c3f25e07d4e8fe04e60ec314640
SHA256: c462a555dda50ed12424a51158666bd3cbe1befb93a34ac81f03548051fa0b50
Homepage: http://www.zfsonlinux.org/
Description-en: command-line tools to manage OpenZFS filesystems
 The Z file system is a pooled filesystem designed for maximum data
 integrity, supporting data snapshots, multiple copies, and data
 checksums.
 .
 This package provides the zfs and zpool commands to create and administer
 OpenZFS filesystems.
Description-md5: 3b2c00b92882937cb7252c01e41d8975
Supported: 9m

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: zfsutils-linux 0.6.5.6-0ubuntu18
ProcVersionSignature: User Name 4.13.0-19.22~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Jan 10 22:26:33 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug curtin uec-images xenial

-- 
You received this bug notification because you are a 

[Bug 1737592] Re: no zfs module in initramfs

[Ryan Harper]

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 seconds.
[^[[0;32m  OK  ^[[0m] Started Apply the settings specified in cloud-config.
 Starting Execute cloud user/final scripts...
[8.616435] cloud-init[1435]: Hit:1 http://archive.ubuntu.com/ubuntu xenial 
InRelease
[8.672908] cloud-init[1435]: Get:2 http://security.ubuntu.com/ubuntu 
xenial-security InRelease [102 kB]
[8.674883] cloud-init[1435]: Get:3 http://archive.ubuntu.com/ubuntu 
xenial-updates InRelease [102 kB]
[8.928164] cloud-init[1435]: Get:4 http://archive.ubuntu.com/ubuntu 
xenial-backports InRelease [102 kB]
[8.995416] cloud-init[1435]: Get:5 http://archive.ubuntu.com/ubuntu 
xenial/universe amd64 Packages [7532 kB]
[9.080891] cloud-init[1435]: Get:6 http://security.ubuntu.com/ubuntu 
xenial-security/main amd64 Packages [409 kB]
[9.283115] cloud-init[1435]: Get:7 http://security.ubuntu.com/ubuntu 
xenial-security/universe amd64 Packages [191 kB]
[9.350155] cloud-init[1435]: Get:8 http://security.ubuntu.com/ubuntu 
xenial-security/multiverse amd64 Packages [3208 B]
[9.442908] cloud-init[1435]: Get:9 http://archive.ubuntu.com/ubuntu 
xenial/multiverse amd64 Packages [144 kB]
[9.516022] cloud-init[1435]: Get:10 http://archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages [683 kB]
[9.579850] cloud-init[1435]: Get:11 http://archive.ubuntu.com/ubuntu 
xenial-updates/universe amd64 Packages [566 kB]
[9.652460] cloud-init[1435]: Get:12 http://archive.ubuntu.com/ubuntu 
xenial-updates/multiverse amd64 Packages [16.2 kB]
[9.716868] cloud-init[1435]: Get:13 http://archive.ubuntu.com/ubuntu 
xenial-backports/main amd64 Packages [4836 B]
[9.780898] cloud-init[1435]: Get:14 http://archive.ubuntu.com/ubuntu 
xenial-backports/universe amd64 Packages [6612 B]
[   10.718880] cloud-init[1435]: Fetched 9861 kB in 2s (4415 kB/s)
[   11.385174] cloud-init[1435]: Reading package lists...
[   11.449013] cloud-init[1435]: Reading package lists...
[   11.561550] cloud-init[1435]: Building dependency tree...
[   11.563580] cloud-init[1435]: Reading state information...
[   11.664585] cloud-init[1435]: The following package was automatically 
installed and is no longer required:
[   11.666506] cloud-init[1435]:   libfreetype6
[   11.667620] cloud-init[1435]: Use 'apt autoremove' to remove it.
[   11.669035] cloud-init[1435]: The following additional packages will be 
installed:
[   11.670778] cloud-init[1435]:   libnvpair1linux libuutil1linux libzfs2linux 
libzpool2linux zfs-doc
[   11.672519] cloud-init[1435]: Suggested packages:
[   11.673680] cloud-init[1435]:   fdutils linux-doc-4.4.0 | linux-source-4.4.0 
linux-tools
[   11.675245] cloud-init[1435]:   linux-headers-4.4.0-103-generic 
samba-common-bin nfs-kernel-server
[   11.676981] cloud-init[1435]:   zfs-initramfs
[   11.678095] cloud-init[1435]: Recommended packages:
[   11.679275] cloud-init[1435]:   grub-pc | grub-efi-amd64 | grub-efi-ia32 | 
grub | lilo zfs-zed
[   11.680847] cloud-init[1435]: The following NEW packages will be installed:
[   11.681995] cloud-init[1435]:   libnvpair1linux libuutil1linux libzfs2linux 
libzpool2linux
[   11.683237] cloud-init[1435]:   linux-image-4.4.0-103-generic zfs-doc 
zfsutils-linux
[   11.811514] cloud-init[1435]: 0 upgraded, 7 newly installed, 0 to remove and 
8 not upgraded.
[   11.813829] cloud-init[1435]: Need to get 22.8 MB of archives.
[   11.815138] cloud-init[1435]: After this operation, 69.7 MB of additional 
disk space will be used.


Using an initrd produced from this branch, the same dep check path shows:

[8.078240] cloud-init[1225]: Cloud-init v. 17.1 running 'modules:config' at 
Thu, 21 Dec 2017 21:06:17 +. Up 7.10 seconds.
[^[[0;32m  OK  ^[[0m] Started Apply the settings specified in cloud-config.
 Starting Execute cloud user/final scripts...
[9.099855] cloud-init[1430]: Hit:1 http://archive.ubuntu.com/ubuntu xenial 
InRelease
[9.102304] cloud-init[1430]: Get:2 http://security.ubuntu.com/ubuntu 
xenial-security InRelease [102 kB]
[9.156567] cloud-init[1430]: Get:3 http://archive.ubuntu.com/ubuntu 
xenial-updates InRelease [102 kB]
[9.412186] cloud-init[1430]: Get:4 http://archive.ubuntu.com/ubuntu 
xenial-backports InRelease [102 kB]
[9.443453] cloud-init[1430]: Get:5 http://security.ubuntu.com/ubuntu 
xenial-security/main amd64 Packages [409 kB]
[9.483278] cloud-init[1430]: Get:6 http://archive.ubuntu.com/ubuntu 
xenial/universe amd64 Packages [7532 kB]
[9.637120] cloud-init[1430]: Get:7 http://security.ubuntu.com/ubuntu 
xenial-security/universe amd64 Packages [191 kB]
[9.701364] cloud-init[1430]: Get:8 http://security.ubuntu.com/ubuntu 
xenial-security/multiverse amd64 Packages [3208 B]
[  

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

[Ryan Harper]

** 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 encountered in other situations.
+ 
+This affects the btrfs-tools package prior to the 3.13 release.
+
+  * Backporting the fix from the upstream repository is required to
+allow Trusty MAAS/Cloud images which use overlayrootfs to create
+btrfs filesystems in the presence of a loopdevice with a missing
+backing file.
+ 
+  * All patches applied are already accepted upstream.  Xenial, Artful,
+and Bionic are not affected.
+
+ 
+ [Test Case]
+ 
+  * On a Trusty 14.04 system with a secondary disk (vdb)
+ - apt-get install btrfs-tools
+ - truncate -s 1G testloop.img
+ - losetup /dev/loop0 testloop.img
+ - mkfs.ext4 /dev/loop0
+ - mount /dev/loop0 /mnt
+ - rm testloop.img
+ - mkfs.btrfs --force /dev/vdb
+ 
+ PASS if mkfs.btrfs returns 0 and /dev/vdb has a btrfs filesystem
+ 
+ FAIL if mkfs.btrfs returns non-zero and /dev/vdb does not have a
+ btrfs filesystem.  mkfs.btrfs returns the error message:
+ 
+ Error: error checking /dev/vdb mount status
+ 
+ [Regression Potential]
+ 
+  * mkfs.btrfs fails to detect that the target device is already mounted
+and an existing btrfs filesystem is destroyed.
+ 
+ 
+ [Original Description]
  # lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04
  
  # apt-cache policy btrfs-tools
  btrfs-tools:
-   Installed: 3.12-1ubuntu0.1
-   Candidate: 3.12-1ubuntu0.1
-   Version table:
-  *** 3.12-1ubuntu0.1 0
- 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.12-1 0
- 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+   Installed: 3.12-1ubuntu0.1
+   Candidate: 3.12-1ubuntu0.1
+   Version table:
+  *** 3.12-1ubuntu0.1 0
+ 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.12-1 0
+ 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  
  # mkfs.btrfs --force /dev/vdd   succeeds
  
- # # mkfs.btrfs --force /dev/vdd 
+ # # mkfs.btrfs --force /dev/vdd
  Error: error checking /dev/vdd mount status
  
  # strace -f mkfs.btrfs --force /dev/vdd
  
  stat("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0), ...}) = 0
  lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4180, ...}) = 0
  lstat("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0), ...}) = 0
  open("/sys/block//loop0/loop/backing_file", O_RDONLY) = 5
  fstat(5, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fe8bd73c000
  read(5, "/root.tmp.img (deleted)\n", 4096) = 24
  close(5)= 0
  munmap(0x7fe8bd73c000, 4096)= 0
  lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4180, ...}) = 0
  lstat("/dev/vdd", {st_mode=S_IFBLK|0660, st_rdev=makedev(253, 48), ...}) = 0
  lstat("/root.tmp.img (deleted)", 0x7ffeaa3f0bf0) = -1 ENOENT (No such file or 
directory)
  close(4)= 0
  munmap(0x7fe8bd73d000, 4096)= 0
  close(3)= 0
  write(2, "Error: error checking /dev/vdd m"..., 44Error: error checking 
/dev/vdd mount status
  ) = 44
  exit_group(1)   = ?
  +++ exited with 1 +++
  
  It appears that mkfs.btrfs doesn't like the loop device, /dev/loop0
  which has a deleted backing file.
  
- root@ubuntu:~# cat /sys/block/loop0/loop/backing_file 
+ root@ubuntu:~# cat /sys/block/loop0/loop/backing_file
  /root.tmp.img (deleted)
  root@ubuntu:~# ls -al /root.tmp.img
  ls: cannot access /root.tmp.img: No such file or directory
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: btrfs-tools 3.12-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-135-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Wed Nov 29 02:58:04 2017
  ProcEnviron:
-  TERM=vt102
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=vt102
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: btrfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735046

Title:
  mkfs.btrfs error checking mount status of loop device backing_file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1735046/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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: bcache psmouse virtio_blk virtio_net 
virtio_scsi pata_acpi floppy
[   20.937686] bcache: bch_journal_replay() journal replay done, 558 keys in 30 
entries, seq 593
[   20.937782] bcache: register_cache() registered cache device vdc
[   20.940029] CPU: 0 PID: 176 Comm: bcache_allocato Not tainted 
4.13.0-19-generic #22-Ubuntu
[   20.940825] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[   20.942112] task: 95c0ef878000 task.stack: a8f1c0394000
[   20.942903] RIP: 0010:_raw_spin_lock_irqsave+0x22/0x40
[   20.943606] RSP: 0018:a8f1c0397d00 EFLAGS: 00010046
[   20.944232] RAX:  RBX: 0246 RCX: 
[   20.944849] RDX: 0001 RSI: 0003 RDI: 0b84
[   20.945503] RBP: a8f1c0397d08 R08: c0376a20 R09: aaab
[   20.946125] R10: a8f1c0369000 R11: 95c0fd120e78 R12: 0b84
[   20.946745] R13:  R14: 0021 R15: 
[   20.947366] FS:  () GS:95c0ffc0() 
knlGS:
[   20.948112] CS:  0010 DS:  ES:  CR0: 80050033
[   20.948124] bcache: register_bdev() registered backing device vda2
[   20.949494] CR2: 0b84 CR3: 2fb8e000 CR4: 06f0
[   20.950311] Call Trace:
[   20.950607]  try_to_wake_up+0x40/0x480
[   20.951048]  wake_up_process+0x15/0x20
[   20.951490]  bch_bucket_alloc+0xa5/0x320 [bcache]
[   20.952043]  ? wait_woken+0x80/0x80
[   20.952387]  bch_prio_write+0x19f/0x340 [bcache]
[   20.952797]  bch_allocator_thread+0x569/0xc80 [bcache]
[   20.953546]  kthread+0x125/0x140
[   20.953869]  ? bch_invalidate_one_bucket+0x80/0x80 [bcache]
[   20.954363]  ? kthread_create_on_node+0x70/0x70
[   20.954764]  ret_from_fork+0x25/0x30
[   20.955083] Code: ff 66 90 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53 
9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f 
b1 17 85 c0 75 06 48 89 d8 5b 5d c3 89 c6 e8 19 63 7c ff 
[   20.956770] RIP: _raw_spin_lock_irqsave+0x22/0x40 RSP: a8f1c0397d00
[   20.957579] CR2: 0b84
[   20.958038] ---[ end trace 2fbf49a9fcc4299e ]---
[   21.088078] tsc: Refined TSC clocksource calibration: 2397.221 MHz
[   21.089038] clocksource: tsc: mask: 0x max_cycles: 
0x228df650ba8, max_idle_ns: 440795214877 ns
Begin: Loading essential drivers ... [  203.088012] raid6: sse2x1   gen()  5302 
MB/s


Launched a vm like this:

 qemu-system-x86_64 -enable-kvm \
  -device virtio-scsi-pci,id=virtio-scsi-xkvm \
  -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 \
  -drive 
file=/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/output/ArtfulBcacheBasic/disks/install_disk.img,id=disk00,if=none,format=raw,index=0
 \
  -device 
virtio-blk,drive=disk00,serial=install_disk.img,logical_block_size=512,physical_block_size=512,min_io_size=512
 \
  -drive 
file=/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/output/ArtfulBcacheBasic/boot/output_disk.img,id=disk01,if=none,format=raw,index=1
 \
  -device 
virtio-blk,drive=disk01,serial=output_disk.img,logical_block_size=512,physical_block_size=512,min_io_size=512
 \
  -drive 
file=/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/output/ArtfulBcacheBasic/disks/extra_disk_0.img,id=disk02,if=none,format=raw,index=2
 \
  -device 
virtio-blk,drive=disk02,serial=extra_disk_0.img,logical_block_size=512,physical_block_size=512,min_io_size=512
 \
  -drive 
file=/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/output/ArtfulBcacheBasic/boot/seed.img,id=disk03,if=none,format=raw,index=3,media=cdrom
 -device virtio-blk,drive=disk03,serial=seed.img -smp 2 -m 1024 -nographic 
-serial 
file:/var/lib/jenkins/slaves/torkoal/workspace/curtin-vmtest-devel-amd64/output/ArtfulBcacheBasic/logs/boot-serial.log

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: curtin

** Attachment added: "serial console boot log"
   
https://bugs.launchpad.net/bugs/1737817/+attachment/5021841/+files/artful-bcache-basic-boot-serial.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737817

Title:
  artful bcache NULL pointer defererence

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 the softlockups in
Artful guests
this continues now in Bionic guests as well.  Host is Xenial, we're now on
Xenial-hwe
 (4.10.0.40-generic x86).

We still see the issue daily.


>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
>

System is used in CI production, so we can't easily test upstream.


>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1722311
>
> Title:
>   softlockups/rcu sched
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1722311/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722311

Title:
  softlockups/rcu sched

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722311/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 patch, Ryan.  I can submit and SRU request.
>
> We should also send this upstream for inclusion in the mainline kernel.
> Is that something you think you can do?  If not, I can do it for you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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.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 [error opening dir]
>
> 0 directories, 0 files
>
> $ sudo dpkg --install linux-image-4.10.0-40-generic_
> 4.10.0-40.44~lp1729145_amd64.deb
> dpkg: warning: downgrading linux-image-4.10.0-40-generic from 4.10.0-40.44
> to 4.10.0-40.44~lp1729145
> (Reading database ... 56846 files and directories currently installed.)
> Preparing to unpack linux-image-4.10.0-40-generic_
> 4.10.0-40.44~lp1729145_amd64.deb ...
> Done.
> Unpacking linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) over
> (4.10.0-40.44) ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postrm.d/x-grub-legacy-ec2
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Setting up linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) ...
> Running depmod.
> update-initramfs: deferring update (hook will be called later)
> Not updating initrd symbolic links since we are being updated/reinstalled
> (4.10.0-40.44 was configured last, according to dpkg)
> Not updating image symbolic links since we are being updated/reinstalled
> (4.10.0-40.44 was configured last, according to dpkg)
> Examining /etc/kernel/postinst.d.
> run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/initramfs-tools
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> update-initramfs: Generating /boot/initrd.img-4.10.0-40-generic
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/update-notifier
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Searching for GRUB installation directory ... found: /boot/grub
> Searching for default file ... found: /boot/grub/default
> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-4.10.0-40-generic
> Found kernel: /boot/vmlinuz-4.10.0-40-generic
> Updating /boot/grub/menu.lst ... done
>
> run-parts: executing /etc/kernel/postinst.d/zz-update-grub
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-4.10.0-40-generic
> Found initrd image: /boot/initrd.img-4.10.0-40-generic
> done
> ubuntu@ubuntu:~$ sudo reboot
> ...
>
> ubuntu@ubuntu:~$ dpkg --list | grep linux-image
> ii  linux-image-4.10.0-40-generic  4.10.0-40.44~lp1729145
>  amd64Linux kernel image for version 4.10.0 on 64
> bit x86 SMP
> ii  linux-image-virtual4.10.0.40.40
>  amd64Virtual Linux kernel image
> ubuntu@ubuntu:~$ sudo tree /dev/bcache
> /dev/bcache
> ├── by-label
> │   ├── backing0 -> ../../bcache2
> │   └── backing1 -> ../../bcache0
> └── by-uuid
> ├── 1375d23f-4780-46d7-9fca-c397f8333685 -> ../../bcache3
> ├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0
> ├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache1
> └── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache2
>
> 2 directories, 6 files
>
>
> On Wed, Dec 6, 2017 at 11:00 AM, Joseph Salisbury <
> joseph.salisb...@canonical.com> wrote:
>
>> I built Xenial, Zesty and Bionic test kernels with your patch.  They can
>> also be downloaded from:
>>
>> http://kernel.ubuntu.com/~jsalisbury/lp1729145/
>>
>> Can those that can reproduce this bug give this test kernel a try?
>>
>>
>> Zesty required upstream commit 4b758df21 as a prereq.  Zesty never got
>> it, since upstream 4.10 is EOL.  Zesty would be the more important test
>> kernel to try due to this difference.
>>
>> Thanks again.
>>
>> --
>> You re

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

[Ryan Harper]

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 [error opening dir]

0 directories, 0 files

$ sudo dpkg --install
linux-image-4.10.0-40-generic_4.10.0-40.44~lp1729145_amd64.deb
dpkg: warning: downgrading linux-image-4.10.0-40-generic from 4.10.0-40.44
to 4.10.0-40.44~lp1729145
(Reading database ... 56846 files and directories currently installed.)
Preparing to unpack
linux-image-4.10.0-40-generic_4.10.0-40.44~lp1729145_amd64.deb ...
Done.
Unpacking linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) over
(4.10.0-40.44) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.10.0-40-generic
/boot/vmlinuz-4.10.0-40-generic
run-parts: executing /etc/kernel/postrm.d/x-grub-legacy-ec2
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.10.0-40-generic
/boot/vmlinuz-4.10.0-40-generic
Setting up linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(4.10.0-40.44 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(4.10.0-40.44 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-40-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-4.10.0-40-generic
Found kernel: /boot/vmlinuz-4.10.0-40-generic
Updating /boot/grub/menu.lst ... done

run-parts: executing /etc/kernel/postinst.d/zz-update-grub
4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-40-generic
Found initrd image: /boot/initrd.img-4.10.0-40-generic
done
ubuntu@ubuntu:~$ sudo reboot
...

ubuntu@ubuntu:~$ dpkg --list | grep linux-image
ii  linux-image-4.10.0-40-generic  4.10.0-40.44~lp1729145
 amd64Linux kernel image for version 4.10.0 on 64
bit x86 SMP
ii  linux-image-virtual4.10.0.40.40
 amd64Virtual Linux kernel image
ubuntu@ubuntu:~$ sudo tree /dev/bcache
/dev/bcache
├── by-label
│   ├── backing0 -> ../../bcache2
│   └── backing1 -> ../../bcache0
└── by-uuid
├── 1375d23f-4780-46d7-9fca-c397f8333685 -> ../../bcache3
├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0
├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache1
└── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache2

2 directories, 6 files


On Wed, Dec 6, 2017 at 11:00 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> I built Xenial, Zesty and Bionic test kernels with your patch.  They can
> also be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1729145/
>
> Can those that can reproduce this bug give this test kernel a try?
>
>
> Zesty required upstream commit 4b758df21 as a prereq.  Zesty never got it,
> since upstream 4.10 is EOL.  Zesty would be the more important test kernel
> to try due to this difference.
>
> Thanks again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 Signed-
> off-by, I just forgot to add it in the attached one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

Woot!

I think that did the trick.

ubuntu@ubuntu:~$ cat /etc/cloud/build.info
build_name: server
serial: 20171122
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
ubuntu@ubuntu:~$ set -o vi
ubuntu@ubuntu:~$ dpkg --list | grep linux-image
ii  linux-image-4.13.0-17-generic  4.13.0-17.20~lp1739145
 amd64Linux kernel image for version 4.13.0 on 64
bit x86 SMP
ii  linux-image-virtual4.13.0.17.18
 amd64Virtual Linux kernel image
ubuntu@ubuntu:~$ dpkg --list | grep bcache-tools
ii  bcache-tools   1.0.8-2build1
amd64bcache userspace tools

ubuntu@ubuntu:~$ sudo tree /dev/bcache
/dev/bcache
├── by-label
│   ├── backing0 -> ../../bcache1
│   └── backing1 -> ../../bcache0
└── by-uuid
├── 1375d23f-4780-46d7-9fca-c397f8333685 -> ../../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...@canonical.com>
wrote:

> 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 those that can reproduce this bug give this test kernel a try?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729145
>>
>> Title:
>>   /dev/bcache/by-uuid links not created after reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
>> /+subscriptions
>>
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 those that can reproduce this bug give this test kernel a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 of mount shows it consulting blkid for devices with LABEL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736556

Title:
  mount can exit (success) when it fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1736556/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 the change to linux-signed, there is still a
bug.
In that light, can we get next steps on debugging grub or firmware or
whateever
else is needed to push this along?


On Tue, Dec 5, 2017 at 7:58 AM, Rod Smith  wrote:

> I'd just like to emphasize that, although a change to always install the
> linux-signed kernel on AMD64 systems is necessary to fix this bug, it's
> not sufficient to fix the bug. As noted in my comment #25 (and
> elsewhere), another change is also required -- either a change to Shim
> or GRUB (I don't know which) or a change to how MAAS handles the boot
> process (to have the PXE-booted GRUB read the configuration file from
> the hard disk rather than chainload to GRUB on the hard disk; or perhaps
> a change to the way the handoff is done, if some tweak could bypass the
> bug).
>
> As before, I remain able and willing to test potential fixes.
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1711203
>
> Title:
>   Deployments fail when Secure Boot enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203

Title:
  Deployments fail when Secure Boot enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 <ryan.har...@canonical.com>
wrote:

> 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 bch_cached_dev_emit_change(), but
>> not in bch_cached_dev_run().
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1729145
>>
>> Title:
>>   /dev/bcache/by-uuid links not created after reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
>> /+subscriptions
>>
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 bch_cached_dev_emit_change(), but
> not in bch_cached_dev_run().
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 (development branch)
Release:18.04

2) # apt-cache policy nplan
nplan:
  Installed: 0.30
  Candidate: 0.32
  Version table:
 0.32 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
 *** 0.30 100
100 /var/lib/dpkg/status

3) netplan generate renders a networkd .network file which has [Bridge]
section including  Priority  value set on each of the bridge ports
specified

4) netplan fails to parse the input yaml with

Sample config that should parse:

% cat br-pp.yaml
network:
version: 2
ethernets:
eth0:
match:
macaddress: '52:54:00:12:34:04'
bridges:
br0:
addresses:
- 192.168.14.2/24
interfaces:
- eth0
parameters:
path-cost:
eth0: 50
priority: 22
port-priority:
eth0: 14

% netplan generate
Error in network definition br-pp.yaml line 13 column 16: unknown key 
port-priority


If fixed, then I would expect a /run/systemd/network/10-netplan-eth0.network 
that looks like
[Match]
MACAddress=52:54:00:12:34:00
Name=eth0

[Network]
Bridge=br0
LinkLocalAddressing=no
IPv6AcceptRA=no

[Bridge]
Cost=50
Priority=14

** Affects: nplan (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/1735821

Title:
  netplan needs bridge port-priority support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[Ryan Harper]

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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735821

Title:
  netplan needs bridge port-priority support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735821/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs