This SRU has a regression:
https://bugs.launchpad.net/netplan/+bug/1795343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Title:
Backport netplan.io 0.40 to bionic
To manage notifications ab
Actually there needs to be changes to netplan to emit the correct
IPV6BytesMtu setting to networkd; and then cloud-init can emit the
correct netplan yaml for that. This feature is on the netplan roadmap
here:
https://trello.com/c/nIjLIRSG/6-support-ipv6-mtu-bytes-configuration
** Also affects:
This may now be a cloud-init bug if the support is there since this is
a network-config v1 -> cloud-init renders netplan.
On Fri, Sep 28, 2018 at 9:12 AM Scott Moser wrote:
>
> Hm...
>
> Our tests show that this is not fixed in cosmic or bionic.
>
> https://jenkins.ubuntu.com/server/job/curtin-vm
The comments are unclear what the actual sequence of failure is, but as
comment #4 mentions the tool will automatically listen to the default
port on *ALL* interfaces (0.0.0.0).
If you want to manually create one using the existing default port, you
have to delete the 0.0.0.0 entry before adding a
Can we confirm which version of curtin you have installed?
** Changed in: curtin (Ubuntu Trusty)
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/1791006
Title:
deplo
Public bug reported:
1) lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2) $ apt-cache policy bluez
bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
*** 5.48-0ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/ma
On Wed, Aug 29, 2018 at 12:01 PM Joseph Salisbury
wrote:
>
> Thanks for digging up this additional information. I'll investigate
> further. While I do that, the v4.19-rc1 kernel is now out. It might be
> worthwhile to give that one a go, and see if the fix was already
> committed to mainline:
>
On Wed, Aug 29, 2018 at 8:41 AM Dimitri John Ledkov
wrote:
>
> Do we need this in bionic?
Yes
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671951
>
> Title:
> networkd should allow configuring IPV6 MTU
>
> To man
https://www.spinics.net/lists/linux-bcache/msg04869.html
https://www.spinics.net/lists/linux-bcache/msg05774.html
On Tue, Aug 28, 2018 at 2:30 PM Ryan Harper wrote:
>
> It's always been a locking issue, so either misuse (or missing) locks
> in the bcache attach/detach path, or g
https://patchwork.kernel.org/patch/10094201/
diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
index d4f80786e7c2..3890468678ce 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dt
It's always been a locking issue, so either misuse (or missing) locks
in the bcache attach/detach path, or generic locking changes to block
layer path I'd think.
I'll see if I can find any hits on those oops tracebacks too
On Tue, Aug 28, 2018 at 2:29 PM Ryan Harper w
FAILED: Kernel 4.15-rc1 up to bc631943faba6fc3f755748091ada31798fb7d50
Attached is the oops of the failure.
** Attachment added: "rc1-bisect7-oops.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5181823/+files/rc1-bisect7-oops.txt
--
You received this bug notif
PASS: Kernel 4.15-rc1 (bisect6) up to
87eba0716011e528f7841026f2cc65683219d0ad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
mkfs.ext4 over /dev/bcache0 hangs
To manage notifications
PASS: Kernel 4.15-rc1 (bisect5) up to
6b457409169b7686d293b408da0b6446ccb57a76
I've 2600 seconds of uptime with over 800 loops in the test-case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
FAILED: Kernel 4.15-rc1 up to f48f66a962a54c3d26d688c3df5441c9d1ba8730
Attached is the oops of the failure.
** Attachment added: "rc1-bisect4-oops.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5181417/+files/rc1-bisect4-oops.txt
--
You received this bug notif
We're looking to support this use-case in netplan in the near future.
I'll update this bug with some details on what changes we'll need to
cloud-init to support this use-case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
FAILED: Kernel 4.15-rc1 up to f17b9e764dfcd838dab51572d620a371c05a8e60
Attached is the oops of the failure.
** Attachment added: "rc1-bisect3-ops.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5178807/+files/rc1-bisect3-ops.txt
--
You received this bug notific
test kernel 4.15-rc1 up to abb62c46d4949d44979fa647740feff3f7538799
FAILED
** Attachment added: "kernel oops for 4.15-rc1 up to
abb62c46d4949d44979fa647740feff3f7538799"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5175947/+files/rc1-bisect2-oops.txt
--
You rece
test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699
FAILED
** Attachment added: "kernel oops for
4.15-rc6-up-to-d8887f1c7289848e74c92bd4322789a9cd7de699"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5175379/+files/rc6-bisect1-oops.txt
--
You recei
test kernel 4.15-rc6 up to d8887f1c7289848e74c92bd4322789a9cd7de699
FAILED
Attaching oops.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
mkfs.ext4 over /dev/bcache0 hangs
To manage
4.14 Final: OK
4.15-rc1:OK
I started a further bisect:
4.15-rc9:FAIL
4.15-rc5:OK
4.15-rc7:FAIL
4.15-rc6:OK
So, it appears something between rc6 (last known good) and rc7 (FAIL)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
4.10:
Status: OK
Comment: Survived 30 minute loop over recreating with no issues.
4.13:
Status: OK
Comment: Survived 30 minute loop over recreating with no issues.
4.15:
Status: FAIL
Comment: triggered within less than a minute of the loop.
Kernel Trace:
[ 122.500943] Oops: [
Hi Daniel,
Thanks for commenting. I don't believe your issue is the same as this
bug (kernel issue with e1000e driver in the 4.15 kernel). Rather it
appears that you're booting a cloud image outside of a cloud and without
any cloud configuration.
Cloud-init only runs if it detects that it has b
I can recreate on upstream:
# uname -r; dmesg | tail -n 16
4.18.0-041800rc7-generic
[ 967.657492] INFO: task bcache_allocato:14240 blocked for more than 120
seconds.
[ 967.664138] Not tainted 4.18.0-041800rc7-generic #201807292230
[ 967.669641] "echo 0 > /proc/sys/kernel/hung_task_timeou
I'll see if I can reproduce on the mainline kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784665
Title:
mkfs.ext4 over /dev/bcache0 hangs
To manage notifications about this bug go to:
http
I think I've got one. It doesn't always hang the mkfs, but it does
wedge bcache in a few ways.
[ 484.322546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 484.326230] INFO: task bcache_allocato:32503 blocked for more than 120
seconds.
1) when it occurs, a backi
** Attachment added: "bcache-basic-repro.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5170528/+files/bcache-basic-repro.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
We've just had a second occurrence of this, same kernel, but with
Xenial. (Xenial HWE Edge kernel 4.15.0-29) with the same scenario,
mkfs.ext4 a /dev/bcache0.
I'll see if I can recreate by stressing things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
We've had plenty of successful runs on this kernel. I suspect io load
or something else may trigger this. We've only seen it once out of tens
of not hundr
Public bug reported:
$ cat /proc/version_signature
Ubuntu 4.15.0-29.31-generic 4.15.18
$ lsb_release -rd
Description:Ubuntu Cosmic Cuttlefish (development branch)
Release:18.10
$ apt-cache policy linux-image-`uname -r`
linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candi
The parameters are supported; but you cannot "try" that configuration
out temporarily. The 'try' subcommand attempts to keep the current
configuration around, generate and apply the "new" config, and allow you
to confirm if things are working and if not, it will restore the
original config prior t
> I assume curtin only does the wipefs when the bcache devices are
attached, correct?
Yes; curtin probes the disks that are present and activates them as
needed. Bcache is activated by the kernel itself if the metadata header
is present on any block device.
If the disk is not attached to the end
On Fri, Jun 29, 2018 at 11:20 AM Gábor Mészáros
wrote:
>
> That I can later, not now.
> What I see now though is mds are not clean and resync started:
Yes; the updated curtin does a number of things to prevent this from
happening.
1) we wipe the first and last 1M of the raid device itself
2) we
Can you provide the curtin install log?
** 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/1778704
Title:
redeployment of node with bcache fails
T
Hello,
I believe this issue is resolved in this commit[1].
There is a new version of curtin for Xenial which contains the fix. Can you
update curtin to the latest?
curtin | 18.1-17-gae48e86f-0ubuntu1~16.04.1 | xenial-updates/universe |
all
--
You received this bug notification because you are
The commit:
https://git.launchpad.net/curtin/commit/?id=4bf7750b6010f0483b22ff626eab58d6a85bb072
** 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/1
I've just seen that upstream systemd v239 claims to support IPV6MtuBytes
https://lwn.net/Articles/758128/
* networkd's .network files now support a new IPv6MTUBytes= option for
setting the MTU used by IPv6 explicitly as well as a new MTUBytes=
option in the [Route] section to configure the MTU t
On Tue, Jun 19, 2018 at 9:41 AM Hadmut Danisch wrote:
>
> dnsmasq _after_ networking?
>
> Isn't it part of networking and should be running and ready for other
> services depending on networking?
Yes, but it's complicated; see below.
>
>
> (my guess is that Ubuntu has never defined the targets v
I see, interesting. The dnsmasq.service does not wait for
network-online.target;
This appears to be a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1531184
In addition to the netplan config to ensure it waits for your bridge
to come up, you need to delay dnsmasq.service u
This has been fixed in upstream curtin here:
https://git.launchpad.net/curtin/commit/?id=4bf7750b6010f0483b22ff626eab58d6a85bb072
At some point the live installer will pick up the newer curtin release
with this fix included.
** Changed in: curtin (Ubuntu)
Status: Confirmed => Fix Committe
There isn't yet a way to allow DNS overrides and DHCP on the same
interface. That is, the DHCP response from the server may include DNS
entries so the custom nameserver values are not automatically appended
to an existing DHCP configuration.
Generally adding/overriding DHCP response values isn't
https://netplan.io/faq#example-for-an-ifupdown-legacy-hook-for-post-
uppost-down-states
You can use a networkd-dispatcherd to hook on vlan0 becoming routeable
and then start/restart the dnsmasq service;
On Fri, Jun 15, 2018 at 12:36 PM, Hadmut Danisch wrote:
> So it is not possible to have an i
In your netplan example config, keyword 'optional' means that systemd-
networkd won't wait until this interface is up before declaring to
systemd that the network is online. THis means dnsmasq is starting
before the vlan0 interface is created.
If you remove the optional value that should ensure i
The underlying curtin bug was resolved here:
https://git.launchpad.net/curtin/commit/?id=4bf7750b6010f0483b22ff626eab58d6a85bb072
That's been released in Xenial through Cosmic
curtin | 18.1-17-gae48e86f-0ubuntu1~16.04.1 | xenial-updates
I can't tell what version of curtin gets packaged, the iso
I don't think so.
>From a hypervisor perspective, general function I think is more
important than running as fast as possible. Historically users have
always enabled additional speed by swapping out emulated devices for
paravirtual ones.
For users of the command line, changing the default will h
RE: bikeshedding on the name; I don't think -large or -big maps well
the the feature, which is more like -cpu host; ie, give the host cpu
attributes to the guest vcpu.
In this case, we're asking to have host physical addressing bits
applied to the guest vcpus.
So maybe -hpb for HostPhysicalBits?
This bug is believed to be fixed in curtin in version18.1-17-gae48e86f-
0ubuntu1. If this is still a problem for you, please make a comment and
set the state back to New
Thank you.
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You received this bug notification because y
I'm not certain we can rule out the charm; the observant behavior is
that the compute nodes do not get enrolled.
Certainly the lack of a nova-compute node being registered has some
touch point to the charms.
The follow-up I think comes from the Openstack team to walk through
where the charm leaves
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 net_setup_link'. Howeve
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 coldplug, so any .link
"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 conf
** 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 (L
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.
https://bugs.la
** 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 curtin
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 Na
nces.
On Tue, May 22, 2018 at 9:21 PM, Jason Hobbs wrote:
> ls -alR /sys on bionic http://paste.ubuntu.com/p/nrxyRGP3By/
>
> The bionic kernel has also bumped:
> Linux aurorus 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:14:36 UTC
> 2018 aarch64 aarch64 aarch64 GNU/Linux
>
>
** 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 Ubunt
** 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-fixe
** 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 subscribe
** 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 Ubunt
** 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 subscribe
** 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 Ubunt
*** This bug is a duplicate of bug 1768893 ***
https://bugs.launchpad.net/bugs/1768893
The bcache message is *NOT* a failure in the kernel;
That message is emitted when a bcache device is reregistered, the
kernel will emit the changed event to ensure
that udev will create /dev/bcache/by-{uuid
t;> 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:
>>>> Comparing the kernel logs, on Xenial, the second nic comes up:
>>>>
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 bio
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 be because curtin failed
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:
##
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 to
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
** 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
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)
*
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 eve
Some package level deltas that may be relevant:
ii linux-firmware 1.173
ii linux-firmware 1.157.18
ii pciutils 1:3.3.1-1.1ubuntu1.2
ii pciutils 1:3.5.2-1ubuntu
libvirt0:arm644.0.0-1ubuntu7~cloud0
libvirt0:arm644.0.0-1ubuntu8
Les
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
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
B
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.
https://bugs.launchpad.ne
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 rena
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
wrote:
> T
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 update-initramfs -u
>
> This
-link.rules
bin/readlink
On Fri, May 11, 2018 at 9:35 AM, Ryan Harper 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 root.
>
> Here's the
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 definiti
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 itself
> in the initramfs!
The .
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
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 /run/netplan or /run/systemd/netw
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 network-con
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 because
** 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:
Yes; this was a an upgraded system.
On Thu, May 3, 2018 at 5:28 PM, Colin Ian King
<1768...@bugs.launchpad.net> wrote:
> This seems to only occur with a Xenial -> Artful or Xenial -> Bionic
> upgrades and not Artful -> Bionic.
>
> --
> You received this bug notification because you are subscribed
Public bug reported:
% apt-cache policy libnvpair1linux
libnvpair1linux:
Installed: 0.7.5-1ubuntu15
Candidate: 0.7.5-1ubuntu15
Version table:
*** 0.7.5-1ubuntu15 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
% lsb_release -rd
D
What's the process for upgrading from Artful to Bionic?
do-release-upgrade -d ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768118
Title:
/etc/netplan/50-cloud-init.yaml fails silently with no d
On Mon, Apr 30, 2018 at 12:14 PM, Colin Ian King
<1760...@bugs.launchpad.net> wrote:
> The code actually polls /dev/zfs until it appears. The issue here is
> that it does not appear after 10 seconds, and then it gives up.
Yes, you're right.
Would it make sense to have zfsutils know it's running i
If they're going to modprobe and are waiting on udev, then I would like
them to do something like
udevadm settle --exit-if-exists=/dev/zfs
That means they can exit early without paying the 10s by default value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for report.
I've seen this on drives which use msdos logical/extended partitioning.
** Changed in: curtin (Ubuntu)
Importance: Undecided => High
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bu
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=6ef92c98
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Can you provide the curtin config and install log ?
On Thu, Apr 26, 2018 at 1:26 AM, Po-Hsu Lin wrote:
> Hi Scott,
>
> any update for the curtin fix in Xenial?
>
> (curtin-common 18.1-1-g45564eef-0ubuntu1~16.04.1, still not working)
> Thanks
>
> --
> You received this bug notification because you
This last passed our vmtest on April 19th, using shim-signed
1.33.13-0ubuntu2
[ 247.040363] cloud-init[993]: ['install-grub', '--uefi', '--update-nvram',
'/tmp/tmpfx83n0fv/target']
[ 247.044415] cloud-init[993]: moved
etc/default/grub.d/50-cloudimg-settings.cfg out of the way
[ 247.047645] cl
https://github.com/CanonicalLtd/netplan/pull/22 has merged now.
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765833
Title:
I've given this a test in LXD on my system which triggers the RA stall;
after upgrading it does not wait for an RA before marking the interface
configured and also confirmed that it does not regress the case where
there are existing RA's on the network; those are still received. Note
that we see e
I've built netplan.io locally with this PR and it resolves the issue. We see
we're passing the 100 value through into networkd, and it gets the ms suffix.
Then in the journal, after the bond has been started, it is ready right away.
root@rharper-b2:~# apt-cache policy netplan.io
netplan.io:
I
https://github.com/CanonicalLtd/netplan/pull/22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765833
Title:
bond intervals default to seconds; breaks existing configs
To manage notifications about
601 - 700 of 1382 matches
Mail list logo