[Bug 1713537] [NEW] iscsi-targets don't quit session on shutdown

Public bug reported: 1. Artful (MAAS Image)[a] 2. open-iscsi 2.0.874-4ubuntu1 3. On shutdown, all iscsi sessions to be stopped and unmounted 4. Iscsi stops but does not stop sessions and shutdown is blocked/hung [^[[0;32m OK ^[[0m] Reached target Shutdown. [ 125.666350] connection4:0: ping

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

The dyn-conf generator in the initramfs does this ## This file is generated by cloud-initramfs-dyn-netconf auto lo iface lo inet loopback manual ens3 iface ens3 inet dhcp dns-nameservers 10.0.0.2 0.0.0.0 dns-search maas However, the resolvconf dir in /run/resolvconf does not have antything

[Bug 1713537] Re: iscsi-targets don't quit session on shutdown

Due to some change in behavior of iscsi, we now trip up over not disconnecting the targets after unmounting them from the target. The disconnect code is call with the target dir path (Which isn't valid any more due to being unmounted). We should definitely umount the targets first (to flush data

[Bug 1713537] Re: iscsi-targets don't quit session on shutdown

** Changed in: open-iscsi (Ubuntu) Status: New => Invalid ** Changed in: curtin (Ubuntu) Status: New => In Progress ** Changed in: curtin (Ubuntu) Assignee: (unassigned) => Ryan Harper (raharper) -- You received this bug notification because you are a member of Ub

Re: [Bug 1713537] Re: iscsi-targets don't quit session on shutdown

Well bummer, pre-artful, it doesn't find the session data. Let's try logging out before umounting (which still syncs devices). On Mon, Aug 28, 2017 at 7:21 PM, Launchpad Bug Tracker < 1713...@bugs.launchpad.net> wrote: > ** Branch linked: lp:~raharper/curtin/trunk.fix-iscsi-shutdown > > -- > You

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning)

Can you include /proc/cmdline used? cloud-init is configuring networking from the kernel cmdline, as ip= is seen on the cmdline 2017-08-18 22:56:13,931 - stages.py[INFO]: Applying network configuration from cmdline ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete -- You

[Bug 1713537] Re: iscsi-targets don't quit session on shutdown

** Changed in: curtin (Ubuntu) Status: In Progress => Fix Committed ** Changed in: curtin (Ubuntu) Assignee: Ryan Harper (raharper) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

Possibly not then, the device that was in use has a net-.conf file; If we don't have iscsi then what other script is going to create the .interface file? Here's the conf file for ens3 (the device in use) % cat run/net-ens3.conf DEVICE='ens3' PROTO='dhcp' IPV4ADDR='10.0.0.54'

[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

I re-ran the recreate on a daily artful image, updated cloud-init in the image to use the udevadm trigger as before and noticed that it still fails to apply the MTU to the second interface. Taking the suggestion of including a udevadm control reload, I further modified the image to add that

[Bug 1671951] Re: networkd should allow configuring IPV6 MTU

** Branch linked: lp:~raharper/curtin/trunk.vmtest-remove-bug-timers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications

[Bug 1721156] [NEW] networkd does not set bridge forward delay value correctly

Public bug reported: 1) # lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 2) # apt-cache policy systemd systemd: Installed: 234-2ubuntu10 Candidate: 234-2ubuntu10 Version table: *** 234-2ubuntu10 500 500

[Bug 1721156] Re: networkd does not set bridge forward delay value correctly

It turns out that if STP is enabled, then one cannot disable the forward delay, and a value < 2 is not compatible with STP. If I set stp: false in netplan, then we get: # cat /run/systemd/network/10-netplan-br0.netdev [NetDev] Name=br0 Kind=bridge [Bridge] AgeingTimeSec=250 Priority=22

[Bug 1721847] Re: sru cloud-init 2017-10-06 (17.1-18-gd4f70470-0ubuntu1)

** Attachment added: "1718287.log" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1721847/+attachment/4974298/+files/1718287.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721847

[Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

I suspect because in bionic/artful we're missing resolvconf package, that the systemd-resolved service ends up starting later in boot. The systemd-resolved-update-resolveconf.{service,path} require /sbin/resolvconf to run; this service had a path-based trigger that would get hooked whenever

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

Should we re-open the grub2 task then? or add a shim task? -- 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

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

I cannot verify this one yet, the previous SRU to xenial has blocked this: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1713142 On Thu, Nov 23, 2017 at 11:00 AM, Łukasz Zemczak <1669...@bugs.launchpad.net > wrote: > Hello Ryan, or anyone else affected, > > Accepted nplan into

[Bug 1734490] [NEW] Graphics mode never switches from console mode on Artful kernel

Public bug reported: Booting a Lenovo S-10 Ideal pad on the 4.13 kernel in Artful fails to bring up the Graphical display (only the mouse shows). Console-mode works fine. Switch back to previous release kernel (4.10) works fine. Booting includes an intel graphics assertion about plane B

[Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

Booting with 'nomodeset' allows system to boot into graphics mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734490 Title: Graphics mode never switches from console mode on Artful kernel To

[Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

[4.710462] WARNING: CPU: 1 PID: 168 at /build/linux-2JtliJ/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x128/0x140 [i915] [4.710466] Modules linked in: i915(+) psmouse ahci r8169 i2c_algo_bit libahci drm_kms_helper pata_acpi ssb syscopyarea sysfillrect

[Bug 1734490] Re: Graphics mode never switches from console mode on Artful kernel

https://bugs.freedesktop.org/show_bug.cgi?id=102929 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734490 Title: Graphics mode never switches from console mode on Artful kernel To manage

[Bug 1668347] Re: Unable to set bridge_portpriority with networkd

This bug was filed to address *port* priority, not the bridge priority. As mentioned, systemd (networkd) lacks a per-port priority setting; it should mirror path-cost which takes an interface and value, then the interfaces have a [Bridge] section which has the value. -- You received this bug

Re: [Bug 1668347] Re: Unable to set bridge_portpriority with networkd

, once netplan has support for this syntax (which is almost identical to path-cost) Then cloud-init.net.netplan renderer will need an update to support generating netplan yaml with the correct structure. On Wed, Nov 29, 2017 at 9:52 AM, Ryan Harper <1668...@bugs.launchpad.net> wrote: >

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

Public bug reported: # 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/

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

to the rootfs; fall back to util-linux mount that does # not understand -o move mount -n -o move /dev ${rootmnt}/dev || mount -n --move /dev ${rootmnt}/dev Let's see if that helps resolve the "missing" symlinks. On Thu, Nov 30, 2017 at 10:27 AM, Ryan Harper <ryan.har...@canonical.com> wr

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

** Bug watch added: Debian Bug tracker #844775 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844775 -- 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

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

So, /dev/bcache/by-uuid is not getting created. That's the same kernel bug I filed. And, if they were, I think they'd get moved properly. init-bottom/udev script does the following: # Stop udevd, we'll miss a few events while we run init, but we catch up udevadm control --exit # move the /dev

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

It looks like there is some ordering issues: This is a grep through /run/udev/links ; these are checked by udev-dev # find . -name 'b250*' ./\x2fdisk\x2fby-uuid\x2f0a270acb-56b8-4498-8bad-b3bb149fe869/b250:1 ./\x2fdisk\x2fby-uuid\x2f92b0868d-7e56-4956-8e55-2c90ebee4a72/b250:0

[Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

We will still need something that helps ensure systemd-resolved runs we reach network-online.target; and I suspect (though I've not validated yet) that we really want systemd-resolved to be running prior to systemd-networkd such that systemd-networkd can relay DNS configuration info retrieved

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

Cherry pick upstream commit which resolves dealing with loopfiles when doing mount checks. https://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs- progs.git/commit/?id=d06b30feb9cb99e3684b5709159ca59cf811f517 I've built a deb from this and tested that this works when a loopdevice is

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

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

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

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

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

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

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

; ../../bcacheN On Thu, Nov 30, 2017 at 7:16 PM, Ryan Harper <ryan.har...@canonical.com> wrote: > It looks like there is some ordering issues: > > This is a grep through /run/udev/links ; these are checked by udev-dev > > # find . -name 'b250*' > ./\x2fdisk\x2fby-uuid\x2f0a27

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

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

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

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

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

Untested patch. Hoping to convey the change that's needed. - decouple emitting a cached_dev CHANGE uevent which includes dev.uuid and dev.label from bch_cached_dev_run() which only happens when a bcacheX device is bound to the actual backing block device (bcache0 -> vdb) - update

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

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

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

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

[Bug 1652822] Re: grub efi doesn't install fs module needed to access root

In analyzing this over in Bug 1731490; grub-install does not check the filesystem of /boot; even if it did, it still needs to do the follwing: 1) copying the proper modules into /boot/efi/EFI/ubuntu/x86_64-efi/ 2) updating /boot/efi/EFI/ubuntu/grub.cfg to insmod the required modules for the the

[Bug 1732917] Re: 17.1 update breaks EC2 nodes

Is is possible for you to paste the entire /var/log/cloud-init.log file? The attached log only shows one stage of cloud-init boot. In particular, cloud-init local mode will attempt to bring up a network interface to talk to Ec2 metadata service to collect network config; Given the failure path in

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

No one in this thread has answered how MAAS or curtin knows that it should install the -signed version of linux-image. Once that knowledge is passed on, we can work out if curtin can detect that or if maas can and specify which kernel package to use. On Thu, Nov 16, 2017 at 3:25 PM, Steve

[Bug 1721808] Re: sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done-xenial ** 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

[Bug 1721808] Re: sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

** Attachment added: "maas qa/ci test results on curtin from xenial-proposed" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1721808/+attachment/5003027/+files/maas-xenial-proposed-console.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1721808] Re: sru curtin 2017-10-06 - 0.1.0~bzr532-0ubuntu1

** Attachment added: "artifacts from maas qa run on curtin from xenial-proposed" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1721808/+attachment/5003040/+files/maas-qa-artifacts-curtin-xenial-proposed.zip -- You received this bug notification because you are a member of Ubuntu

[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

** Changed in: curtin 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/1573982 Title: LVM boot problem - volumes not activated after upgrade to Xenial To manage

Re: [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

On Wed, Nov 1, 2017 at 8:11 AM, Dimitri John Ledkov wrote: > I have merged the netplan code to that effect in netplan master now - > i.e. generate reloads udevadm rules. > > However, I have now realised something. > > MTUBytes can be set in two places: NetDev.MTUBytes key

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

Mainline kernel does not help; it fails the same way and also has a bug that's fixed in the Ubuntu kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667078 Here's the details from the mainline test: ubuntu@a-unsolar-melonie:~$ dpkg --list | grep linux-image ii

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

To recreate: Add a second disk (any size will do) and split the disk into 4 equal partitions. Then make-bcache -C /dev/vdb1 make-bcache -B /dev/vdb2 make-bcache -B /dev/vdb3 make-bcache -B /dev/vdb4 Note, you can see the proper symlinks created at this time: ls -al /dev/bcache/by-uuid/

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

This fails on Xenial -> Artful. I've not yet tested Trusty, but I suspect it's just a latent bug in the bcache driver. I'll grab the upstream kernel and provide results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1575779] Re: hostnamectl fails under lxd unpriv container

Likely related, but in Artful systemd-networkd is setting the hostname and has a 10 second timeout: # systemctl status --no-pager -l systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)

Re: [Bug 1575779] Re: hostnamectl fails under lxd unpriv container

I can confirm that if I set PrivateNetwork=no that hostnamed runs and boot is magically 10 seconds faster. On Thu, Nov 9, 2017 at 1:46 PM, Stéphane Graber wrote: > Someone with systemd knowledge should check what PrivateNetwork actually > does. The name implies it's

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Bug 1726818] Re: vagrant artful64 box filesystem too small

This thread shows up with that xsave warn: https://www.virtualbox.org/pipermail/vbox-dev/2017-May/014466.html Which suggests adding 'noxsave' to the kernel command line as a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

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

Public bug reported: 1. $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Wed, May 9, 2018 at 9:13 AM, Daniel Axtens wrote: > Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and > I've never seen it regenerated. Ah, right, it doesn't regenerate unless you change instance-ids. > > I also don't see anything in

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

Are you providing network config to cloud-init? Otherwise, cloud-init is going to generate a fallback network config like your original, dhcp on one of the interfaces. If you want to persist network changes, you need to add them to a separate netplan yaml config, or provide an updated

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

Investigating, it appears that the interfaces are getting renamed by udev in the initramfs, which pushes their name_assign_type value to 4, and udev refuses to rename an interface if the name_assign_type value is 4. So, I can make this scenario work if I do: 4. sudo update-initramfs -u 5. reboot

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 11, 2018 at 3:25 AM, Daniel Axtens wrote: > Ryan, I can't get that to work on my systems. What is it that update- > initramfs is supposed to change? I don't see any files in my initramfs > that are generated or read by netplan. Neither do I see netplan

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

I'm just verifying that on my end; note that the 99-default.link is going to be sufficient to trigger a rename from eth0 to ens3; which then prevents any rename once we mount root. Here's the trigger: % /usr/share/initramfs-tools/hooks/udev # copy .link files containing interface naming

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

-link.rules bin/readlink On Fri, May 11, 2018 at 9:35 AM, Ryan Harper <ryan.har...@canonical.com> wrote: > I'm just verifying that on my end; note that the 99-default.link is > going to be sufficient to trigger a rename from eth0 to ens3; which > then prevents any rename once we mount r

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 11, 2018 at 10:18 AM, Daniel Axtens wrote: > Right. Yes, I can replicate that, thanks heaps! Great! > > So to summarise, you can make the rename take effect on boot if you: > 1) copy the files from /run/systemd/network -> /etc/systemd/network > 2) then

[Bug 1768823] Re: netplan ip leases

** Changed in: netplan.io (Ubuntu) Importance: Undecided => Medium ** Changed in: netplan.io (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768823 Title:

[Bug 1724895] Re: MTU not applied on private ethernet interfaces

Can you run cloud-init collect-logs in your instance and attach the tarfile (cloud-init.tar.gz in the current working directory). ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Status: New => Incomplete -- You received this bug notification

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Can you provide the journalctl -b output for the boot that does this rename? Is the reproduce the same, can you provide your steps and I'll replicate. Xenial does not enable netplan by default so we have a different path there at least. On Mon, May 14, 2018 at 9:58 PM, Daniel Axtens

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

And for the xenial deployment version, can we get what's in /etc/network/interfaces* (including the .d)? I'm generally curious w.r.t what interfaces are managed by the OS, and which ones are being delegated to the guests. -- You received this bug notification because you are a member of Ubuntu

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

Please capture: 1) cloud-init collect-logs (writes cloud-init.tar to $CWD) 2) the journal /var/log/journal 3) /etc/netplan and /run/systemd 4) /etc/udev/rules.d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Note, that uvt-kvm is going to use cloud-init; how are you making sure that cloud-init isn't doing the rename itself? Xenial by default doesn't use netplan; it still uses eni; the network configuration generation in cloud-init using eni does create a 70-persistent-net.rules file that handles

[Bug 1772490] Re: bcache: register_bcache() error

ay 21 10:57:05 geodude kernel: [ 49.126408] bcache: register_bcache() error /dev/sda3: device already registered (emitting change event) These are not curtin or kernel errors but expected output. I looked at the qa link but I didn't find the install.log debug output. ** Changed in: curtin

[Bug 1772490] Re: bcache: register_bcache() error

May 21 11:00:42 geodude cloud-init[1643]: curtin: Installation finished. >From the rsyslog, curtin finished the install without error. ** Changed in: curtin Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

Re: [Bug 1772490] Re: bcache: register_bcache() error

Thanks for the log. Curtin installed without error, I'll mark invalid. AFAICT, it booted fine and was instructed to power off. May 21 13:18:51 geodude cloud-init[1676]: Powering node off. May 21 13:18:51 geodude ec2: May 21 13:18:51 geodude ec2:

Re: [Bug 1772490] Re: bcache: register_bcache() error

On Mon, May 21, 2018 at 3:59 PM, Andres Rodriguez wrote: > @Ryan, > > I'm marking this as incomplete for curtin provided that after further > debugging, I can see that the late command that's supposed to send the > "netboot_off" operation is not being sent. > > This could

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

arch64 GNU/Linux > > On Tue, May 22, 2018 at 7:10 PM, Ryan Harper <1771...@bugs.launchpad.net> > wrote: >> Looks like the ls -aLR contains more data; we can compare bionic. >> >> On Tue, May 22, 2018 at 6:53 PM, Jason Hobbs <jason.ho...@canonical.com>

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

** Attachment added: "curtin-vmtest-proposed-b-artifacts.tar.xz" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1772044/+attachment/5143452/+files/curtin-vmtest-proposed-b-artifacts.tar.xz ** Description changed: == Begin SRU Template == [Impact] This release sports both

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

t; wrote: >>> ok; looks like that 4.15.0-22-generic just released and wasn't what I >>> used in the first reproduction... I doubt that's it. >>> >>> On Tue, May 22, 2018 at 4:58 PM, Ryan Harper <1771...@bugs.launchpad.net> >>> wrote: >>>> Com

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

Comparing the kernel logs, on Xenial, the second nic comes up: May 22 15:00:27 aurorus kernel: [ 24.840500] IPv6: ADDRCONF(NETDEV_UP): enP2p1s0f2: link is not ready May 22 15:00:27 aurorus kernel: [ 25.472391] thunder-nicvf 0002:01:00.2 enP2p1s0f2: Link is Up 1 Mbps Full duplex But on

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 25, 2018 at 8:48 AM, Mathieu Trudel-Lapierre wrote: > My recommended course of action for cosmic: > > - drop udevadm (net_setup_link) call from cloud-init This will still be needed in the case that we have a network config with names. Cloud-init runs after udev

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

"This is why I added cloud-init to affected packages -- cloud-init should not be second- guessing the network layer and attempting to do renames / to run" There is no second guessing. In the case where we have no network config, there is no renaming; we accept whatever name is given. If the

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 25, 2018 at 9:09 AM, Mathieu Trudel-Lapierre wrote: > I'm not completely sure where the code lives in cloud-init; it looks a > bit like what's in: > > cloudinit/net/netplan.py > > But the code does read as though it should not be running 'udevadm test- > builtin

Re: [Bug 1770082] Re: systemd-networkd not renaming devices on boot

We really only want to be allowed to rename interfaces that have requested it. This means other interfaces which do not have a set-name directive will have the kernel name. On Thu, May 24, 2018 at 6:56 AM, Mike Jonkmans <1770...@bugs.launchpad.net> wrote: > Things seem to work when i change the

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-17-gae48e86f-0ubuntu1

** Summary changed: - sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1 + sru curtin 2018-05-18 - 18.1-17-gae48e86f-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772044 Title: sru

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

That's not the final conclusion; the issue is still being discussed upstream; in particular as to why only the interface name cannot be modified at runtime by .link files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-17-gae48e86f-0ubuntu1

** 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: implement a supported check to handle i386

[Bug 1772044] [NEW] sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

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: * zfs: implement a supported check to handle i386 (LP: #1768709) *

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

Thanks for the logs. I generally don't see anything *fatal* to libvirt. In the nova logs, I can see that virsh capabilities returns host information. It certainly is failing to find the VFs on the SRIOV device; it's not clear if that's because the device is misbehaving (we can see the kernel

[Bug 1772044] Re: sru curtin 2018-05-18 - 18.1-16-g18835845-0ubuntu1

** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/345951 ** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/345952 ** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/345953

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

To make it more clear; the hardware SRIOV device is different that normal: TL;DR this special device has VFs that have NO PF associated software doesn't understand this Though per comment #3; it seems odd that a Xenial/Queens with the same kernel (HWE) works OK. So some tracing in libvirt/nova

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