*** This bug is a duplicate of bug 2089071 ***
https://bugs.launchpad.net/bugs/2089071
** Also affects: python-defaults (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug n
** Also affects: python2.7 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2089071
Title:
tarfile.py regression
I generated the smaller diff with:
$ diff -u <(awk '{print $6}' lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents )
<(awk '{print $6}' lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents) > file-
list.diff
so one can just see which files were added/removed vs the date/timestamp
change on files that are in both ar
dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output
** Attachment added: "dpkg --contents lxc-dev_5.0.3-2ubuntu8_amd64.deb output"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814927/+files/lxc-dev_5.0.3-2ubuntu8_amd64.deb.contents
--
You received this bug noti
** Patch added: "Diff of dpkg --contents file column only between 7 and 8"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814925/+files/file-list.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
dpkg --contents on lxc-dev_5.0.3-2ubuntu7_amd64.deb
** Attachment added: "output from dpkg --contents on
lxc-dev_5.0.3-2ubuntu7_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2080069/+attachment/5814926/+files/lxc-dev_5.0.3-2ubuntu7_amd64.deb.contents
--
You received this bug
Public bug reported:
1) # lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04
2) # apt-cache policy lxc-dev
lxc-dev:
Installed: 1:5.0.3-2ubuntu7
Candidate: 1:5.0.3-2ubuntu7
Version table:
*** 1:5.0.3-2ubuntu7 500
500 http://archive.u
I'm not sure exactly how the liblxc.a static lib was dropped, but the
attached debdiff resolves this by not removing all .a files (an extra
find|rm is around a comment about removing all .la files) and then
adding the file to lxc-dev.install
This produces a lxc-dev deb which includes the static l
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2000170
Title:
bond interface down: devi
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2000325
Title:
ipv6 duplicate address pr
root@ubuntu:/home/ubuntu# networkctl status eth2-2 --no-pager
● 2: eth2-2
Link File: /run/systemd/network/10-netplan-eth2-2.link
Network File: /run/systemd/network/10-netplan-eth2-2.network
Type:
There are two scenarios: Applying to VM the first time, on subsequent
boots.
On first boot without the updated netplan config, when you first add it
root@ubuntu:/home/ubuntu# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:
** Attachment added: "netplan config for vm2"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637221/+files/50-v4-v6-fail-vm2.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
** Attachment added: "netplan config for vm1"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000325/+attachment/5637220/+files/50-v4-v6-fail-vm1.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
# Create a bridge and add two ports
$ sudo ip link add name atx-fabric0 type bridge
$ sudo ip link set up dev atx-fabric0
$ sudo ip tuntap add atx-fabric0i1p1 user $USER group $USER
$ sudo ip tuntap add atx-fabric0i2p1 user $USER group $USER
# create two focal VM images from focal daily server
$
To reproduce what happens on physical systems I create two VMs with nics
in the same bridge on the host. Booting the first VM up and allowing
the network config to apply, and then when booting the second VM up
layer, as it applies the IPv6 address to the interface in the bridge,
the kernel detects
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://archive.ubuntu.com/ubuntu focal-
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
2) # apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.19
Candidate: 245.4-4ubuntu3.19
Version table:
*** 245.4-4ubuntu3.19 500
500 http://azure.archive.ubuntu.com/ubuntu
@Dan
Just ran into this issue in curtin's vmtest for network_vlan on groovy.
I can confirm that if the netplan config includes the driver match on
the physical interfaces, then the vlans come up just fine.
I was thinking that netplan could inject the driver of the underlying
device into the match
@Rafael
It's in both places:
https://github.com/koverstreet/bcache-tools/pull/1
I can update the PR there as well; though I don't think upstream cares
as Kent's working on bcachefs instead of bcache AFAICT.
> I see that you are trying to come up with something nor relying in the
kernel fix (to
@Rafael
For bcache-tools changes, bcache-export-cached-uuid needs the full path
to bcache-super-show, as PATH is not exported when running from udev.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://
@ddstreet
I'm not sure where upstream is going just yet. For Ubuntu; I think
1) Adjusting the bcache-tools patch to use the full path to bcache-
super-show should change;
2) If we fix (1) then I think we can drop the systemd patch from a bug
fixing perspective; on the openSUSE image I did testi
On Tue, Jun 30, 2020 at 6:35 AM Balint Reczey <1861...@bugs.launchpad.net>
wrote:
> @raharper I've forwarded the systemd fix for you with minimal tidying of
> the commit message https://github.com/systemd/systemd/pull/16317
Thanks!
>
> --
> You received this bug notification because you are su
systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache
backing, caching devices.
** Patch added: "lp1861941-skip-bcache-links.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff
--
You r
Updated test to be a bit more resilient.
** Attachment added: "test-bcache-byuuid-links-fixed.sh"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh
--
You received this bug notification because you are a member of
Tarball of a source package with a fix for this issue:
bcache-tools_1.0.8.orig.tar.gz
bcache-tools_1.0.8-4ubuntu1_amd64.build
bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo
bcache-tools_1.0.8-4ubuntu1_amd64.changes
bcache-tools_1.0.8-4ubuntu1_amd64.deb
bcache-tools_1.0.8-4ubuntu1.debian.tar.xz
bcache
debdiff of the changes
** Attachment added: "bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375722/+files/bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1
--
You received this bug notification because you are a m
OK.
I've reviewed the kernel code, and there are no unexpected changes w.r.t
the CACHED_UUID change event. So I don't think we will need any kernel
changes which is good.
With the small change to the 60-persistent-storage.rules to not attempt
to create a /dev/disk/by-uuid symlink for the backing
@Balint
I do not thing the fix you're released is correct, can you upload a new
version without the scripts?
Also, we should fix make-bcache -B to ensure that cset.uuid is not
initialized; that may be why the kernel thinks it should emit the
CACHED_UUID if the suerpblock of the device has a cset.
Digging deeper and walking through this in a focal vm, I'm seeing some
strange things.
Starting with a clean disk, and just creating the backing device like
so:
make-bcache -B /dev/vdb
We see /dev/bcache0 get created with vdb as the backing device. Now,
after this, I see:
/dev/bcache/by-uuid/
That doesn't explain why they show up sometimes, but not all of
the time.
There are 3 devices in play here.
* The backing device, let's say /dev/vda; this is where we want
to store the data.
* The caching device, let's say /dev/vdb; this holds the cache.
* The bcache device; this only appears
I guess I don't understand why we see this in focal. The two events in
Colin's trace always happen on any Ubuntu kernel. We should see if we
can get another udev trace on bionic that captures both CHANGE events,
one will be from the bcache driver itself, and one is from the block
layer. THe orde
I would very much agree with xnox (it's a duplicate) (and Dan, nothing
for curtin to do);
curtin generated dname rules rely upon pointing to a /dev/bcache/by-
uuid/* symlink which is currently broken per
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941
which at this time points
Probert PR to drop --mknodes:
https://github.com/canonical/probert/pull/88
Curtin MP to drop --mknodes
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/383141
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I don't think this is the right fix. We need to test that it doesn't
prevent vgscan from finding and creating /dev/vg/lv device files outside
of of multipath.
The real fix involves:
1) omitting the call to vgmknodes if there are no volume groups present
2) if vgnodes are present, device_mapp
This patch configures the dm_task to use the
DM_UDEV_DISABLE_LIBRARY_FALLBACK udev flag to prevent calls to
dm_mknodes() from using the library fallback code.
Another possible fix would be to obtain a different return code from
vgscan.c where it does not detect any VGs and then calls the mknode
p
Note, the whitespace damage in the patch is not needed, just my text
client cleaning up trailing whitespace.
With this patch applied, vgscan --mknodes no longer creates block
devices in /dev/mapper
root@ubuntu:/dev/mapper# ls -al
total 0
drwxr-xr-x 2 root root 120 Apr 28 16:31 .
drwxr-xr-x 1
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Tags added: uec-images
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1867029
Title:
Pa
On Tue, Feb 25, 2020 at 2:35 PM Scott Moser
wrote:
> this seemed to "just work" for me.
> http://paste.ubuntu.com/p/93dWDPZfZT/
Ah, I didn't check that there was an existing ubuntu/devel branch. Sorry.
I've pushed a MR here:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/
** Patch added: "debdiff showing the changes to upload to fix the bug."
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330894/+files/cloud-utils_0.31-6_to_0.31-7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Attachment added: "tarball of source package to upload"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330895/+files/cloud-utils_0.31-7-gd99b2d76-source.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
@Scott,
cloud-utils isn't quite new-upstream-snapshot out of the box; the debian
dir does not contain the changelog; however, I think I've got this
sorted out. I've a MP I can put up; but it only will show the add of
the changelog file. I'll attach a debdiff and a source package.
--
You recei
Here's the upstream changes to growpart I'm suggesting:
https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-
utils/+merge/379177
I've also proposed on modifications to cloud-init's cc_growpart as a further
method
to aid debugging if this hit as well as some mitigation around the race.
h
** Changed in: curtin (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: curtin (Ubuntu Focal)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util
** Merge proposal linked:
https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379024
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash a
@Alberto
> I thought the installer would work similarly to what the desktop installer
> does with btrfs, where it creates subvolumes for / and /home in the root
> partition (as @ and @home).
>
> On my desktop, when I upgrade I just move @ out of the way (by renaming it)
> and the installer crea
@Lee Thanks for tracking down the util-linux bug.
Since this is broken in 2.34 (eoan/focal); I'm thinking we should use
sysfs to find the parent via device name walking;
Given a kname (nvme0n1p1) of the target partition
# look up sysfs path from kname
% realpath /sys/class/block/nvme0n1p1
/sys/
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-ff-incoming
** Also affects: util-linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: High
Status: Triaged
** Also affect
Yes, this is my read on the issue as well. The trigger is related to
the inotify watch that systemd-udevd puts on the disk. Something that
might help that we could try per xnox's comment around use of flock.
if growpart were to flock /dev/sda (we need to sort out what flags are
needed to prevent
Verified Eoan systemd 242-7ubuntu3.7 correctly sets IPv6 MTU
Verified Bionic systemd 237-3ubuntu10.39 correctly sets IPv6 MTU
** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5326389/+files/bug-167195
Verified VLANs on Eoan using systemd 242-7ubuntu3.7 from -proposed
correctly set the MTU to 1500 when specified in the netplan config.
** Attachment added: "curtin vmtest logs for vlan mtu verification"
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5326388/+files/bug-1846232-curt
Cloud-init service starts and will run growpart, etc
Feb 06 00:37:26 ubuntu systemd[1]: Starting Initial cloud-init job
(pre-networking)...
Feb 06 00:37:37 test-xrdpdnvfctsofyygmzan systemd[1]: Starting Initial
cloud-init job (metadata service crawler)...
Something has modified sdb1 (growpart/s
Eoan vmtests for vlan MTU checks now pass:
(neipa) vlan-mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkVlan/logs/install-serial.log
[ 131.271209] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64 242-7ubuntu3.3 [126 kB]
[ 131.281683] cl
** Attachment added: "curtin vmtest logs for vlan mtu issue"
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5325684/+files/bug-1846232-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Curtin vmtest verification for bionic using systemd from -proposed has
run successfully.
(neipa) ipv6_mtu % egrep "237-3ubuntu10.34"
output/BionicTestNetworkMtu/logs/install-serial.log
[ 126.923480] cloud-init[1176]: Get:10 http://archive.ubuntu.com/ubuntu
bionic-proposed/main amd64 libsystemd
Curtin vmtest verification for eoan using systemd from -proposed has run
successfully.
(neipa) ipv6_mtu % egrep "242-7ubuntu3.3"
output/EoanTestNetworkMtu/logs/install-serial.log
[ 136.520219] cloud-init[765]: Get:12 http://archive.ubuntu.com/ubuntu
eoan-proposed/main amd64 libnss-systemd amd64
** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5325665/+files/bug-1671951-curtin-vmtest-verification.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1859858
Title:
udev has truncated ID_SERIAL value for scsi disk
Status in systemd package i
Public bug reported:
1.
root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info
build_name: server
serial: 20200106
root@ubuntu:/home/ubuntu# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
2.
root@ubuntu:/home/ubuntu# apt-cache policy systemd
systemd:
** Summary changed:
- vmtests: test_ip_output failing in vlan tests on eoan
+ networkd pads interface MTU by 4 bytes for vlan even when told not to
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
On Thu, Nov 7, 2019 at 2:41 PM Dan Streetman
wrote:
> > Issuing a second
> > trigger will repeat this.
> > IMO, that's a non-zero amount of time that slows the boot down, so I'd
> like
> > to avoid that.
>
> systemd-udev-trigger.serivce retriggers *everything* at boot (except in
>
an unprivileged
On Thu, Nov 7, 2019 at 11:30 AM Dimitri John Ledkov
wrote:
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
>
> That is not true. whilst sfdisk is deleting, creating, finishing
On Thu, Nov 7, 2019 at 1:30 PM Dan Streetman
wrote:
> > Yes, settle does not help.
>
> Well, I didn't suggest just to settle ;-)
>
Sorry; long bug thread.
> > I'm currently suggesting as a heavy-handed workaround.
>
> I don't really see why you think this is heavy-handed, but I must be
> missi
@ddstreet
Yes, settle does not help.
Re-triggering udevadm trigger --action=add /sys/class/block/sda
Would re-run all of them after the partition change has occurred, which
is what I'm currently suggesting as a heavy-handed workaround.
I would like to understand *why* the udevd/kernel pair exhi
> it will prevent udevd from running the rules against it. Thus
effectively the event will be fired and done, but nothing actually
executed for it.
Interesting, I suspect this is the race we see. The events emitted but
no actions taken (ie we didn't get our by-partuuid symlink created.
> I someh
A couple of comments on the suggested path:
> Imho the sequency of commands should be:
> * take flock on the device, to neutralise udev
+1 on this approach. Do you know if the flock will block
systemd's inotify write watch on the block device which triggers
udevd? This is the typical race we se
On trusty; this complains but works.
ubuntu@ubuntu:~$ dpkg --list | grep util-linux
ii util-linux 2.20.1-5.1ubuntu20.9
amd64Miscellaneous system utilities
ubuntu@ubuntu:~$ cat /proc/partitions
major minor #blocks name
2530
Testing with @ddstreet's systemd ppa, I can confirm that bionic, disco
and eoan correctly set MTU on first boot, no systemd-restart needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launch
@Dan,
Ill try the ppa and report back.
cloud-init is not doing anything special here, we render the config and call
netplan generate.
If we take cloud-init out of the picture, and just have a file in /etc/netplan
it will still fail due to the udev issue you specify. Shouldn't netplan itself
ha
@Balint, after further testing, here's where things are:
-
On LXD Containers
-
On Bionic
1) First boot: neither interface mtu, nor ipv6 mtu is applied.
2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied
3) netplan apply: interface mtu
On Fri, Oct 25, 2019 at 1:31 PM Dan Streetman
wrote:
> I looked at this for a few minutes, and it seems strange that it works
> at all (at boot) since networkd sets the ipv6 mtu before bringing the
> link up, but the kernel resets the ipv6 mtu to the device mtu on link
> up. I must be missing so
I did some more testing today. I upgraded systemd and netplan.io to
disco level, rebooted and tested the MTU settings; disco packages fail
as well. I then upgraded to eoan systemd/netplan.io rebooted and the
MTU settings are correct.
--
You received this bug notification because you are a memb
In the Eoan version of systemd, I can see in the logs these messages:
Oct 24 18:52:32.753746 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/proxy_ndp' to '0'
Oct 24 18:52:32.753848 ubuntu systemd-networkd[1167]: Setting
'/proc/sys/net/ipv6/conf/interface1/use_tempaddr
The original netplan yaml I was testing was simpler, but also failed so
I tried to see if additional settings would make a difference, but it
did not.
network:
version: 2
ethernets:
interface0:
dhcp4: true
match:
macaddress: '52:54:00:12:34:0
I cannot verify this is working on bionic with ipv6 static addresses.
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
root@ubuntu:~# cat /etc/cloud/build.info
build_name: server
serial: 20191021
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-66-generic #75-Ubu
This looks to be related to networkd:
https://github.com/systemd/systemd/pull/12574/commits
Which is automatically added 4 bytes to base interface MTU, even though
we're explicitly setting mtu to 1500 on base interface and vlan.
** Also affects: systemd (Ubuntu)
Importance: Undecided
This can be reproduced in an LXD Eoan container:
lxc launch ubuntu-daily:eoan e1
lxc exec e1
cat > /etc/netplan/50-cloud-init.yaml << EOF
network:
version: 2
ethernets:
eth0:
dhcp4: false
mtu: 1500
vlans:
eth0.2667:
id: 2667
@Dan/Chad I suggest we skip-by this bug number on the eoan vlan test
case;
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1846232
Title:
vmtests: test_ip_output failing i
See comment #20; ipv6 mtu is 1280 -> DEVICE_MTU.
I'm testing something in the middle now.
On Eoan with:
network:
version: 2
ethernets:
ens3:
addresses: [10.5.0.16/16]
gateway4: 10.5.0.1
dhcp4: false
match:
macaddres
err, on Eoan, I used ipv6-mtu 6000.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
Status in cloud-init package
I tested with your single-file approach and that also fails. Note that
bionic now has systemd 237, so maybe something is missing (or regressed)
?
$ apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10.26
Candidate: 237-3ubuntu10.26
Version table:
*** 237-3ubuntu10.26 500
500
I launched a bionic image on serverstack, updated the netplan.io to
proposed, modified the network config to set ipv6-mtu to 6000 and
rebooted.
root@b-test-ipv6-mtu:~# apt-cache policy netplan.io
netplan.io:
Installed: 0.98-0ubuntu1~18.04.1
Candidate: 0.98-0ubuntu1~18.04.1
Version table:
*
On Mon, Aug 26, 2019 at 4:05 AM Tobias Koch <1834...@bugs.launchpad.net>
wrote:
> > (Odds are that whatever causes it to be recreated later in boot would be
> > blocked by cloud-init waiting.)
>
> But that's not happening. The instance does boot normally, the only
> service degraded is cloud-init
On Fri, Aug 23, 2019 at 10:21 AM Dan Watkins
wrote:
> Looking at the comment timestamps, Dan probably didn't see my comment,
> but to reiterate: all the events we expect to be processed _are_
> processed, the issue is that when they are processed they don't always
> end up with the correct partit
On Fri, Aug 23, 2019 at 10:00 AM Dan Streetman
wrote:
> > Dan had put a udevadm settle in this spot like so
> >
> > def get_size(filename)
> >util.subp(['udevadm', 'settle'])
> >os.open()
>
> if you know you've just changed (e.g.) /dev/sda, possibly its kernel-
> generated udev events
The sequence is:
exec growpart
exec sgdisk --info # read-only
exec sgdisk --pretend # read-only
exec sgdisk --backup # read-only copy
# modification of disk starts
exec sgdisk --move-second-header \
--delete=PART \
--new=PART \
--typecode --pa
Public bug reported:
Installing into a chroot without /run mounted, grub's os-prober calls
into lvs for details and it waits a very long time. I believe this is
fixed upstream:
https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=3ebce8dbd2d9afc031e0737f8feed796ec7a8df9
1. Eoan
2. lvm2 2.03.
I'm marking the cloud-init task invalid; I don't believe cloud-init did
anything wrong; but please set the task back to New if you have new
information showing that cloud-init didn't do something quite right.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notifi
Hi, I don't believe this is a cloud-init bug. Cloud-init wrote the two
certificate files requested.
2018-05-02 08:55:00,913 - stages.py[DEBUG]: Running module ca-certs () with
frequency once-per-instance
2018-05-02 08:55:00,914 - handlers.py[DEBUG]: start:
init-network/config-ca-certs: running
** Changed in: netplan
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Looks like this issue, I think:
https://github.com/systemd/systemd/issues/12490
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
https://github.com/lxc/lxd/issues/4656
** Bug watch added: LXD bug tracker #4656
https://github.com/lxc/lxd/issues/4656
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1779156
This is still around. Scott wrote up a script to handle cleaning this
up.
https://gist.github.com/smoser/2c78cf54a1e22b6f05270bd3fead8a5c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.
On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper
wrote:
>
>
> On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
> wrote:
>
>> Using systemd 237-3ubuntu10.10
>>
>> Using:
>> [Match]
>> Name=ens3
>> [Network]
>> DHCP=ipv4
>> IPv6
On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov
wrote:
> Using systemd 237-3ubuntu10.10
>
> Using:
> [Match]
> Name=ens3
> [Network]
> DHCP=ipv4
> IPv6MTUBytes=1600
> [Link]
> MTUBytes=1800
> [DHCP]
> UseMTU=no
> RouteMetric=100
>
Do you put this in the same .network file or .link file?
--
On Mon, Nov 26, 2018 at 11:11 PM Jay Vosburgh
<1671...@bugs.launchpad.net> wrote:
>
> Regarding #2 from comment #19:
>
> As the defined range for the ipv6.mtu is from IPV6_MIN_MTU to the
> device's MTU, and the existing API returns an error if the ipv6.mtu is
> out of range, I think it's reasonable
It seems there are some limitations to what systemd will do with
IPv6BytesMTU.
1) if LinkLocalAddressing is not disabled, it will clobber any
IPv6BytesMTU value set.
[Network]
LinkLocalAddressing=ipv6
Address=10.10.10.10/24
IPv6MTUBytes=1470
This results in: /proc/sys/net/ipv6/conf//mtu having a
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
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:
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
1 - 100 of 321 matches
Mail list logo
