I've made some good progress here.
I found that older version like 4.19 work, so I ran git bisect. I'm
still doing the final check, but it looks like the series that causes
the issue is the one containing these:
d53d2f78cead bpf: Use vmalloc special flag
1a7b7d922081 modules: Use vmalloc special
I can repro on upstream, all the way back to 5.4.0. It might have
existed before that - I haven't tested any earlier yet.
Was the test methodology changed just before this was found? I'm just
wondering why it suddenly appeared ~a year after Focal was released. I
thought it might have been a patch
I can repro this with the latest Focal kernel on:
description: PowerNV
product: 8247-22L (IBM Power System S822L)
Trying to see if I can repro it upstream.
FWIW my opening hypothesis is that something in a percpu data structure
isn't getting updated over hotplug.
--
You received this
I cannot yet explain this, but after bisecting the config, I can repro
this with pseries_le_defconfig + CONFIG_RCU_SCALE_TEST=m
That's weird to me, and I'll continue to investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I tested this on a real ppc64le machine:
root@1325f5985861:/# python3 -c "import math; print(math.exp(-1))"
0.36787944117144233
root@1325f5985861:/# uname -a
Linux 1325f5985861 5.4.0-21-generic #25+lp1866909v202004031128-Ubuntu SMP Fri
Apr 3 18:38:30 UTC 202 ppc64le ppc64le ppc64le
The 5.3.0 HWE kernel also works, which means we now have a good
workaround while we debug things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044
Title:
qla2xxx no longer detects LUNs with
Hi Mauricio,
5.4.0-14 works for me, dmesg attached.
I'll see if an HWE kernel supplied in the bionic repositories also
works, maybe we can use that in the mean time so we don't fall any
further behind on kernel updates while we debug this.
Regards,
Daniel
** Attachment added:
Ah, I was just about to tell you that I have just tried master-next at
a59858e18bc8996f8c96d307a33e504b079dc541 ! I think that is the same sha
that ended up being tagged as -89, so I think it provides us with the
same information.
Sadly -89 also doesn't seem to work; dmesg attached.
I don't know
Hi Mauricio,
Thanks for the prompt answer! After a lot of messing around to get a
remote console, I can finally test. It looks like -88 doesn't work. I'm
attaching a dmesg from -88 and -72. I will build and test master-next
next.
Regards,
Daniel
** Attachment added: "dmesg from -88"
** Attachment added: "dmesg from -72"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329133/+files/dmesg-72
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5327820/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044
Public bug reported:
We have an IBM BladeCentre Hx5 with a number of blades running Ubuntu
18.04.3. Storage is attached over Fiber Channel.
They all boot fine with 4.15.0-72 - the qla2xxx detects all the LUNs. On
4.15.0-74 and 4.15.0-76, the qla2xxx driver loads but the LUNs are not
detected.
My colleague has verified all 4 versions. In all cases, on supported
hardware, the test now operates as expected: the secret does not leak
unless the mitigation is manually turned off.
I notice the SRU verification is happening a bit sooner than I expected
- when do you expect these kernels to be
The embargo has expired so I'm making this public now.
** Description changed:
Hi,
Recently you would have been notified about CVE-2019-18660 via email to
the linux-distros private mailing list. In short, it is a bug in the
Spectre v2 class affecting powerpc.
We have developed
Hi Michael R,
I tried to apply your patches to test them and support the effort to get
them included in the Bionic kernel, but I'm having some trouble applying
them:
ubuntu@dja-bionic:~/bionic$ git am
../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch
Patch format detection
OK, so with the magic of debug symbols and gdb on Cosmic:
(gdb) run
...
ens8: Gained IPv6LL
Assertion 'link->state == LINK_STATE_SETTING_ADDRESSES' failed at
../src/network/networkd-link.c:803, function link_enter_set_routes(). Aborting.
...
(gdb) up
#3 0x5566b194 in
Never mind, I can reproduce on Cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
systemd-networkd core dumps in bionic-proposed
To manage notifications about this bug go to:
Oof, sorry! It's not clear to me from the bug report and subsequent
comments - is it just Bionic that's affected, or is it also Cosmic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818340
Title:
** Description changed:
+ SRU Justification
+ =
+
+ [Impact]
+
+ Some users see panics like the following when performing fstrim on a
+ bcached volume:
+
+ [ 529.803060] BUG: unable to handle kernel NULL pointer dereference at
0008
+ [ 530.183928] #PF error:
** Changed in: nplan (Ubuntu)
Assignee: Daniel Axtens (daxtens) => (unassigned)
** Changed in: nplan (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
The user has verified that the -proposed kernel resolves their issue.
Regards,
Daniel
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812760
Title:
networkd: [Route] PreferredSource not working in *.network files
To manage notifications about this bug go to:
from a surprising behaviour to a less
surprising behaviour, but it's worth pointing out.
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
** Changed
The OpenPower partner reports that their system is fixed with this
kernel.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
I just upgraded to cosmic and have hit the issue described in debian bug
#9065955 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906955 -
mbsync won't connect to e.g. gmail because of SSL errors.
I downloaded 1.3.0-2 from Debian and it works. Would it be possible
Hi,
I have a patch which I believe fixes your issue:
https://www.spinics.net/lists/linux-bcache/msg06997.html
It looks like it will go in to the 5.1 kernel, and I will propose it for
backporting to earlier Ubuntu kernels.
Regards,
Daniel
--
You received this bug notification because you are a
Hi,
Thanks Eric.
I specifically tested the version from Trusty: 0.10.5-1ubuntu0.14.04.1.
I tested it by enabling cachefilesd and using dd to get the disk to
about 95% full.
With 0.10.5-1, starting cachefilesd with a full disk caused the process
to spin at 100% cpu usage. With the version from
User has verified the Xenial version. I have verified the Trusty
version.
Regards,
Daniel
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810372
Title:
Infinite busy-loop trying to cull when cache space
I think I have discovered the cause: https://lore.kernel.org/linux-
block/87h8e9ii2l@linkitivity.dja.id.au/
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The full .diff.tar.gz is attached.
** Attachment added: "cachefilesd_0.10.5-1ubuntu1.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/1810372/+attachment/5227284/+files/cachefilesd_0.10.5-1ubuntu1.diff.gz
--
You received this bug notification because you are a member of
It turns out the package uses the cdbs system rather than quilt, so
providing a debdiff is a bit tricky. Here's the patch that I applied,
the result is at
https://launchpad.net/~daxtens/+archive/ubuntu/builder/+build/16226405
and it works on my test system, and I am asking the original reporter to
understood and backports with minimal effort.
** Affects: cachefilesd (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Here's a test case for the NULL pointer dereference in ACL handling.
** Attachment added: "aclcrasher.txt"
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+attachment/5221005/+files/aclcrasher.txt
--
You received this bug notification because you are a member of Ubuntu
This is the warc infinite loop test case. Unlike the other files, it's
*not* encoded, and I use ./bsdtar -Oxf warcloop.warc to see the looping
behaviour.
** Attachment added: "warcloop.warc"
(as with the other test cases, it's in plain text, convert it back with
xxd -r aclcrasher.txt aclcrasher)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794909
Title:
Memory corruption in RAR
Hi Seth,
I've pushed them to https://github.com/libarchive/libarchive/pull/1105
Thanks for walking me through the Ubuntu process.
Regards,
Daniel
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
I've checked that the proposed Xenial AWS kernel works - it boots
successfully and uses the deadline scheduler by default on a t2.micro
instance.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
SRU Justification
=
[Impact]
An IBM OpenPower partner reports their system with a bunch of NVMe
drives fails the NVMe init due to some drives taking PCIe EEH errors.
[Fix]
Pick patch db2173198b9513f7add8009f225afa1f1c79bcc6 upstream.
[Testing]
IBM
** Description changed:
A user reports that using an i40e with intel_iommu=on with the Xenial GA
kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
tree driver more recent than the version shipped with Xenial solves the
issue.
[Impact]
Corrupted data is
Public bug reported:
A user reports that using an i40e with intel_iommu=on with the Xenial GA
kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
tree driver more recent than the version shipped with Xenial solves the
issue.
[Impact]
Corrupted data is returned from the
** Description changed:
In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by
default and cannot use the old I/O scheduler.
[Impact]
blk-mq is not as fast as the old request-based scheduler for some workloads
on HDD disks.
[Fix]
Amazon Linux has a commit which
Public bug reported:
In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by
default and cannot use the old I/O scheduler.
[Impact]
blk-mq is not as fast as the old request-based scheduler for some workloads on
HDD disks.
[Fix]
Amazon Linux has a commit which reintroduces the
Hi,
For Xenial:
daniel_axtens_canonical_com@dja-202158:~$ sudo apt install
google-compute-engine-oslogin=20180905+dfsg1-0ubuntu1~16.04.1
...
Get:1 http://au.archive.ubuntu.com/ubuntu xenial-proposed/universe amd64
google-compute-engine-oslogin amd64 20180905+dfsg1-0ubuntu1~16.04.1 [76.7 kB]
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663280
Title:
Serious performance degradation of math functions
To manage notifications about this bug go to:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798706
Title:
Incomplete linking with boost_regex
To manage notifications about this bug go to:
-shlibdeps: warning: symbol _ZN5boost9re_detail13get_mem_blockEv used by
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
found in none of the libraries
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Daniel Axtens (daxtens)
Status
-shlibdeps: warning: symbol _ZN5boost9re_detail13get_mem_blockEv used by
debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so
found in none of the libraries
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Daniel Axtens (daxtens)
Status
** Description changed:
+ SRU Justification
+ =
+
+ [Impact]
+
+ * Severe performance hit on many maths-heavy workloads. For example, a
+ user reports linpack performance of 13 Gflops on Trusty and Bionic and
+ 3.9 Gflops on Xenial.
+
+ * Because the impact is so large (>3x)
** Description changed:
SRU Justification
-
[Impact]
A kernel BUG is sometimes observed when using fscache:
[4740718.880898] FS-Cache:
[4740718.880920] FS-Cache: Assertion failed
[4740718.880934] FS-Cache: 0 > 0 is false
[4740718.881001]
Hi Steve,
No worries, that sounds fair enough. I will file the bugs as separate
issues in the next few days then.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
Public bug reported:
SRU Justification
-
[Impact]
A kernel BUG is sometimes observed when using fscache:
[4740718.880898] FS-Cache:
[4740718.880920] FS-Cache: Assertion failed
[4740718.880934] FS-Cache: 0 > 0 is false
[4740718.881001] [ cut here
Hi,
I added this to my netplan-config-tester and it's turned up a couple of
issues with NetworkManager.
1) If a static IPv4 address is specified and link-local: [ipv4] is
specified, there is no link-local address added. The documentation
doesn't make this clear; it only refers to DHCP
Hi,
This works on reboot but not so well after the system boots.
Say I have the following file:
network:
version: 2
ethernets:
ens7:
dhcp4: true
match:
macaddress: 52:54:00:b4:02:6e
set-name: myif1
optional: true
** Changed in: glibc (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: glibc (Ubuntu Xenial)
Assignee: (unassigned) => Daniel Axtens (daxtens)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I haven't found the time to do this yet, sorry. Is it still an issue on
the current Xenial kernel?
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742658
Title:
Hi Matt,
I don't think this is documentation-only: it was rendered incorrectly
out to networkd - see my comment #4.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756701
Title:
This has been fixed in Cosmic. I have attempted to nominate it for
Xenial and Bionic for backporting.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Committed
** Changed in: netplan
Status: Fix
) finally check using cat /proc/fs/fscache/stats | grep -i pages ;
free -h , cat /proc/meminfo and page-types -r -b lru
to ensure all pages are freed.
[Regression Potential]
Limited to cachefiles.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (da
** Changed in: linux (Ubuntu)
Assignee: Daniel Axtens (daxtens) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783246
Title:
Cephfs + fscache: unable to handle kernel N
Public bug reported:
Hi,
I installed trousers on my Dell XPS 13, and the following error
occurred:
Aug 06 12:03:45 linkitivity trousers[11173]: * Starting Trusted Computing
daemon tcsd
Aug 06 12:03:45 linkitivity trousers[11173]: /etc/init.d/trousers: 32: [:
/dev/tpm0: unexpected operator
** Description changed:
== SRU Justification ==
[Impact]
Oops during heavy NFS + FSCache use:
- [81738.886634] FS-Cache:
+ [81738.886634] FS-Cache:
[81738.888281] FS-Cache: Assertion failed
[81738.889461] FS-Cache: 6 == 5 is false
[81738.890625] [ cut here
Oops, my mistake, there are already LP bugs covering these issues.
Regards,
Daniel
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
mportance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784864
Title:
Various fscache/cachefiles bugs
To manage notifications about t
Yes, we have closed the support case on our end at their request.
Apparently increasing the reservation ratio has helped.
Paulus - Hi! Thanks for the info and clearing up some of my
misunderstandings. Great to hear from you and I hope things are going
well at OzLabs :)
--
You received this bug
Hmm, maybe it needs to be explicitly set for NM when the user sets it to
off. I'll look into it at some point soon, hopefully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750392
Title:
nplan
I can't reproduce this with a bnx2x card. What card are you using?
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781203
Title:
Bonding "parameters" not supported
To manage notifications about this bug go to:
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726695
Title:
Routes are not correctly documented in man pages
To manage
Sorry, I meant duplicate of LP: #1746419
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781203
Title:
Bonding "parameters" not supported
To manage notifications about this bug go to:
I agree it is a bug. It is an unfortunate mix of netplan and systemd
decisions/features/bugs causing the issue.
Do you mind if we mark this as a duplicate of LP: #1781203? It's the
same root cause (netplan apply cannot change bond parameters) just with
a different presentation (netplan try). Once
It looks like at least some of this changed between Bionic and Cosmic -
here with a netplan 0.39:
root@netplan:~# netplan apply
Error in network definition /etc/netplan/50-cloud-init.yaml line 5 column 0:
unknown key xxnetwork
root@netplan:~# echo $?
78
--
You received this bug notification
been in mainline
since v4.16. So the risk of regression is well contained.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Daniel Axtens (daxtens)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm marking this as confirmed as the behaviour has come up in LP:
#1735318.
** Changed in: netplan
Status: Incomplete => Confirmed
** Changed in: nplan (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Should it though? That will, for example, terminate any tcpdump
processes bound to the bond, it will disrupt currently running
connections, etc. Maybe we could do it but we'd want to put it behind a
--force option or something, I think.
--
You received this bug notification because you are a
This hit me too.
I'm not sure how netplan can fix this - it looks like it's generating
pretty sensible configuration files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781652
Title:
should be
** Changed in: nplan (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750392
Title:
nplan cannot enable IPv6 privacy extensions
To manage
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
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/1746419
Title:
bond
Netplan apply cannot change bond parameters either. You would either
need to delete the bond and then run netplan apply, or just reboot. See
LP: #1746419
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This all seems to work on Bionic, so closing this issue.
** Changed in: nfs-ganesha (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743302
Title:
wrong
Public bug reported:
Hi,
I've run in to a problem in man page generation to do with fonts.
Something like:
Note that **``rdnssd``**(8) is required to use RDNSS with networkd. No extra
software is required for NetworkManager.
gets rendered wrongly: the bold text goes right to the end
** Changed in: netplan
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
To manage notifications
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
It looks like this and bug LP: #1736965 are duplicates.
I have proposed https://github.com/CanonicalLtd/netplan/pull/36 as a
fix.
Regards,
Daniel
** This bug has been marked a duplicate of bug 1736965
) => Daniel Axtens (daxtens)
** Changed in: nplan (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735944
Title:
cannot route IPv6 addresses
To
Hi,
I have reproduced this on bionic, and proposed the following patch to
fix it: https://github.com/CanonicalLtd/netplan/pull/36
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I have it working for me using my ipv6 test bench
(https://github.com/daxtens/ipv6-config-demos)
Systemd-networkd:
root@slaac-rdnss-networkd:~# ip a list temporary
root@slaac-rdnss-networkd:~# sudo nano /etc/netplan/60-ipv6.yaml # add
ip6-privacy: true
root@slaac-rdnss-networkd:~# sudo
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741910
Title:
ath6kl_sdio does not support unbinding
To manage notifications
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748629
Title:
'netplan help' doesn't work as expected
To manage notifications
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735317
Title:
Invalid YAML in docs
To manage notifications about this bug go to:
Thanks, done.
** Changed in: nplan (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619258
Title:
netplan should allow NICs to be disconnected and
** Changed in: nplan (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751151
Title:
Installing via IPv6 results in invalid netplan yaml
To manage
Hi,
I'm trying to triage some old bugs so apologies if this comes out of the
blue.
Line numbers being wrong is a known issue - see LP: #1752956.
>From what you've posted, it looks like your bridges stanza isn't
sufficiently indented - it should be at the same level of indent as
ethernets. Do
Hi,
Are you able to test a package for me? I have uploaded netplan.io
0.39+dja1 to https://launchpad.net/~daxtens/+archive/ubuntu/builder - if
you could add the ppa and install that version of netplan, it adds a
`ip6-privacy` key. Currently I've only wired up the networkd backend,
but if that
Hmm, this will need a YAML key added. I'll see if I can whip something
up.
** Changed in: nplan (Ubuntu)
Assignee: (unassigned) => Daniel Axtens (daxtens)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Hi,
I wonder if this is the replug code doing stupid stuff. That code is not
long for this world anyway, but we can probably get it kicked out faster
if it is indeed at fault.
Could you run 'netplan --debug apply' and provide its output please? And
the network card/driver that you're using
*** This bug is a duplicate of bug 1736975 ***
https://bugs.launchpad.net/bugs/1736975
Hi,
(I'm trying to tidy up some old bugs so apologies if this seems a bit
out of the blue!)
This is a known issue and I'm pretty sure what you describe is an exact
duplicate of LP: #1736975. (perhaps
Hi!
(I'm going through and trying to clean up some old bugs, so apologies if
this is a bit out of the blue.)
There's some work in progress to do this. I originally had a PR that
would make it configurable but cyphermox has a WIP commit that will just
tear out the replugging entirely:
Hi!
(I'm going through and trying to clean up some old bugs, so apologies if
this is a bit out of the blue.)
I just want to confirm how you got this /etc/netplan/01-netcfg.yaml. If
I understand you correctly it was created by the installer and you had
to insert the quotes manually. Is that
This has been in a released version of netplan.io since 0.32. Are we
right to mark this as Fix Released for nplan? It looks like LP: #1664844
has been marked as Fix Released too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I am told that this is the same machine but not while it was currently
showing symptoms - due to the intermittent nature of the problem it
was taken some time later. This matches what I see in the logs so I
have no reason to doubt it.
Regards,
Daniel
--
You received this bug notification
1 - 100 of 259 matches
Mail list logo
