** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs integration
To
(Moved the groovy task back to New, not sure if that's the right
process!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874464
Title:
NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
And this is what I see on 5.9.0-050900rc3-generic:
Sep 04 15:05:02 surprise kernel: [ cut here ]
Sep 04 15:05:02 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit
queue 0 timed out
Sep 04 15:05:02 surprise kernel: WARNING: CPU: 0 PID: 0 at
I saw this traceback on the 4.15.18 mainline build:
Sep 04 14:47:41 surprise kernel: [ cut here ]
Sep 04 14:47:41 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit
queue 0 timed out
Sep 04 14:47:41 surprise kernel: WARNING: CPU: 11 PID: 0 at
I just saw this again on 5.8.0-18-generic, and this time I did not
manually modify my networking state; I installed the new kernel and
rebooted into it, and the problem exhibited immediately. (Fortunately,
for whatever reason, a reboot into Windows and back to -18 _has_ come up
with networking,
I just saw this again on 5.8.0-18-generic, and this time I did not
manually modify my networking state; I installed the new kernel and
rebooted into it, and the problem exhibited immediately. (Fortunately,
for whatever reason, a reboot into Windows and back to -18 _has_ come up
with networking,
** Changed in: cloud-init (Ubuntu Groovy)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Groovy)
Assignee: (unassigned) => Dan Watkins (oddbloke)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, so the issue we're dealing with here is that bug 1877491 fixed the
grub install device for _new_ NVMe instances, but it did not fix it on
existing NVMe instances. So, for existing instances, they will still
have an incorrect grub install device configured (something like
/dev/sda).
grub has
The upstream issue was closed due to the age of the version I reported
with; groovy has a more recent version so I've opened
https://github.com/neomutt/neomutt/issues/2549 for this issue.
** Bug watch added: github.com/neomutt/neomutt/issues #2549
https://github.com/neomutt/neomutt/issues/2549
Public bug reported:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
** Changed in: curtin (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/1881003
Title:
sru curtin 2020-05-27 - 20.1-0ubuntu1
To manage notifications
A fix for this landed in https://github.com/canonical/cloud-
init/commit/456fb55744a1acc6bd2f464b7656a9c33d0b7ac5
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "the artifacts from the upstream-tests focal curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5392911/+files/curtin-vmtest-manual-rerun-f-artifacts.tar.xz
** Description changed:
== Begin SRU Template ==
[Impact]
This release
We have now completed SRU verification across all releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881003
Title:
sru curtin 2020-05-27 - 20.1-0ubuntu1
To manage notifications about this
Currently our focal Jenkins jobs for curtin are failing due to an
unrelated issue, so two manual runs of curtin's CI were performed for
focal: the first had some tests fail due to bugs in the test code (that
have since been fixed upstream), so the second reruns the upstream test
code for those
** Attachment added: "the artifacts from the initial focal curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5392910/+files/curtin-vmtest-manual-run-f-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> It is definitely not Hetzner's task to fix Ubuntu.
To be clear, cloud-init is not used only on Ubuntu; I believe that
Hetzner's outage would have this effect across the majority of Linux
distributions.
And, that aside, I don't think this characterisation is fair: we're
suggesting that if
I'm trying to understand if there is any work still required on this bug
for cloud-init. I've tested two network configurations (in lxd
containers). The first:
version: 2
ethernets:
eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 1337
As this is just a passthrough to netplan,
This landed in https://github.com/canonical/cloud-
init/commit/3d06abc2e0017436dadbf9c26fefa9f95368db9a, and I have since
uploaded a new cloud-init package to groovy; it should migrate shortly.
** Changed in: cloud-init (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received
Hi Travis,
Thanks for the logs! I can't tell definitively if this is the problem
from the logs we collect, but snapd has failed to seed the system, and I
know that cloud-init waits for seeding to complete before executing the
modules and final stages (in case the seeded snaps are required by the
If Hetzner has (or starts to provide) a way of determining instance ID
without using the network, we'd be more than happy to accept patches to
use that in cloud-init. However, as it sounds like the issue here is
Hetzner's internal services being unreliable, rather than a cloud-init
issue, I'm
No worries, I've just moved it there. :)
** Also affects: wpasupplicant (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: Triaged => 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/1886080
Title:
lxd cloud_tests fail to export images on latest/stable
To
> Possible to try older kernel releases? Like 4.15?
I'm happy to try; how would I go about installing them on groovy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874464
Title:
NETDEV WATCHDOG:
I have tested both rc3 and rc4; neither addresses the issue for me. I
am seeing a slightly different call trace now though (this is from an
rc3 boot):
Jul 06 08:44:48 surprise kernel: [ cut here ]
Jul 06 08:44:48 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit
(I'm now running groovy on this system, in case that changes anything.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874464
Title:
NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
To
** Changed in: paramiko (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398322
Title:
python-paramiko in trusty is incompatible with OpenSSH in vivid
To
** Changed in: cloud-init (Ubuntu)
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/1796917
Title:
cloud-init fails to run on latest cosmic minimal image
Hi Eduardo,
Thanks for using cloud-init, and for the bug report! We believe that
this bug is fixed in the version of cloud-init that is currently going
through the SRU process to be backported to focal. (Specifically, the
fix was proposed in https://github.com/canonical/cloud-init/pull/315.)
Thanks for the info, Eddy! Based on those logs, I've confirmed that
this isn't an error condition. Examining the code, it looks like we
intentionally set the hostname differently on RHEL-based systems vs all
other distros: compare the default behaviour in
https://github.com/canonical/cloud-
I've also seen this while running `ubuntu-bug /var/crash/...`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884221
Title:
`ubuntu-bug` fails with "UnboundLocalError: local variable 'project'
** Attachment added: "the artifacts from the bionic MAAS CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385349/+files/maas-bionic.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "the artifacts from the xenial MAAS CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385348/+files/maas-xenial.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "the artifacts from the local bionic curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385127/+files/curtin-vmtest-local-run-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "the artifacts from the manual bionic curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385126/+files/curtin-vmtest-manual-run-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "the artifacts from the Jenkins bionic curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385124/+files/curtin-vmtest-proposed-b-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Three runs of curtin's CI were performed for bionic: the first, our
regular Jenkins run had some tests fail due to bugs in the test code
(that have since been fixed upstream), so the second reruns the upstream
test code for those tests against the -proposed package. This second
run had some
** Attachment added: "the artifacts from the manual xenial curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385117/+files/curtin-vmtest-manual-run-x-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "the artifacts from the Jenkins xenial curtin CI run"
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+attachment/5385116/+files/curtin-vmtest-proposed-x-artifacts.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Two runs of curtin's CI were performed for xenial: the first, our
regular Jenkins run had some tests fail due to bugs in the test code
(that have since been fixed upstream), so the second reruns the upstream
test code for those tests against the -proposed package.
** Attachment added: "xenial
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting on
To manage notifications about
Hi Eddy,
Thanks for taking the time to file the bug, and for including a log
snippet! To get the full debugging information we'll need to analyse
this issue, can you please run `cloud-init collect-logs` on an affected
instance and attach the tarball it produces to the bug? Once done,
please
*** This bug is a duplicate of bug 1825413 ***
https://bugs.launchpad.net/bugs/1825413
** This bug has been marked a duplicate of bug 1825413
mdadm, mkfs, other io commands hang, stuck task, bad rip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
In the curtin integration tests, we have seen this kernel panic in the
last of our three daily runs (unfortunately we don't have history before
that):
[ 94.443649] cloud-init[1011]: Running command ['blkid', '-o', 'full'] with
allowed return codes [0] (capture=True)
[
OK, I just did the following (all on 5.4.0-33-generic):
* modified /etc/default/grub to include " pcie_aspm=off" in the kernel command
line
* `update-grub`
* `reboot`
* double-checked that "pcie_aspm=off" was in the kernel command line, then
booted
* once booted and logged in, I disabled
I'll try the command line change after my morning meetings; here's the
requested debug output:
$ sudo lspci -xxxs 00:01.3
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
00h-0fh) PCIe GPP Bridge
00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00
10: 00 00 00 00 00 00
Hi Kimball,
Thanks for the bug report! We need more information to be able to
triage it further. Could you please run `cloud-init collect-logs` on an
affected instance and attach the tarball it produces to this bug? (Once
done, please move the cloud-init task back to New and we'll take a look.
** Changed in: curtin (Ubuntu)
Status: Confirmed => In Progress
** Changed in: curtin (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This doesn't seem to be a curtin bug to me; feel free to disagree (with
reasoning!).
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Thanks for the triage Dimitri, I agree that the cloud-init docs could be
improved here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878066
Title:
ds=nocloud and ds=nocloud-net for automated
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878066
Title:
Created attachment 9146163
raw_data.json
I don't see any errors in the Browser Console, only a warning:
"unreachable code after return statement" in "injected.js:7:2". I've
copied the raw data and attached it here.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Marcus,
Note that ifupdown is no longer a supported networking path on focal, so
you may want to look into migrating your network configuration to
netplan regardless to avoid other issues like this cropping up going
forward.
That said, I agree that we don't need to express a hard dependency
This now happens with misspellings:
$ locales
Command 'locales' not found, did you mean:
command 'locale' from deb libc-bin (2.31-0ubuntu9)
Try: sudo apt install
$ dpkg -l libc-bin
ii libc-bin 2.31-0ubuntu9 amd64GNU C Library: Binaries
This is particularly
Moving this to Incomplete until we hear back about whether the netplan
fixes affect this. (Please move back to New if it's still an issue!)
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'd be happy to assist in debugging this, is there anything I can do to
help track it down?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874464
Title:
NETDEV WATCHDOG: enp5s0 (r8169): transmit
Here are the NetworkManager logs when I first disabled my networking
(note that ensp5s0 does get its link up reported correctly, but no
traffic seems to go over it):
Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1626]
manager: disable requested (sleeping: no enabled: yes)
Apr 23
Public bug reported:
Running focal on a desktop, I accidentally clicked "Enable networking"
in nm-applet, disabling my networking. When I clicked it again to
reenable it, my networking did not return. After unsuccessfully poking
at it for a while, I rebooted and saw the below (and still no
Public bug reported:
Steps to reproduce:
In a pristine directory:
$ echo foo > a
$ echo foo > b
$ ag foo # This is as expected
a
1:foo
b
1:foo
$ ag --nofilename foo # But not this
foo
foo
Actual behaviour:
"foo\n\nfoo"
Expected behaviour:
"foo\nfoo"
(This is particularly annoying when
Dave, Balint suggests that the latest systemd upload may have fixed
this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/comments/16
Would you be able to perform another test and let us know if this is
still an issue?
--
You received this bug notification because you are a
On Wed, Apr 22, 2020 at 02:53:48PM -, Jonathan Kamens wrote:
> I understand that, but in this particular case we're talking about a
> transition from a deb to a snap, not a snap update.
Aha, apologies, I misread your previous comment.
> Apparently there's special logic in update-manager to
(https://github.com/canonical/ubuntu-advantage-client/issues/949 is
perhaps related.)
** Bug watch added: github.com/canonical/ubuntu-advantage-client/issues #949
https://github.com/canonical/ubuntu-advantage-client/issues/949
--
You received this bug notification because you are a member of
On Wed, Apr 22, 2020 at 10:24:41AM -, Jonathan Kamens wrote:
> I'm a bit concerned about that, though, because the reason why I didn't
> get that update is because I pretty much exclusively use apt to do my
> updates, and apparently that's no longer sufficient to get all the
> updates needed
How does this relate to bug 1870346?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870410
Title:
wireless does not work on boot on RPi 3s
To manage notifications about this bug go to:
** Changed in: cloud-init (Ubuntu)
Assignee: Roufique Hossain (roufique) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866562
Title:
cloud-init should also try to use
** Changed in: cloud-init (Ubuntu Trusty)
Assignee: Roufique Hossain (roufique) => (unassigned)
** Changed in: cloud-init (Ubuntu)
Assignee: Roufique Hossain (roufique) => (unassigned)
** Changed in: cloud-init
Assignee: Roufique Hossain (roufique) => (unassigned)
--
You
Looking at the journal, I see that systemd-networkd does know about
wlan0, and reports Link UP for it when cloud-init would expect system
networking to be configured:
Mar 18 19:32:59.099186 ubuntu systemd-networkd[1121]: wlan0: Link UP
is before:
Mar 18 19:32:59.107823 ubuntu systemd[1]:
cloud-init has support for ubuntu-drivers, it's not clear from this bug
what work we would need to do so I've marked our task Incomplete.
** Changed in: cloud-init
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On Thu, Apr 16, 2020 at 07:31:02PM -, Jeremy Norris wrote:
> I hope that 9d7b35ce was also picked up, as that was the actual fix for this
> issue?
> 0c5c7367 appears simply to be a follow-up change to the new unit test that
> was included in 9d7b35ce.
Yep, the messaging is a little
at a higher level, that the Oracle data source is used in each
case.
(Thanks to xnox for the sponsorship!)
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: open-iscsi (Ubuntu)
Status: New => In Progress
--
You received th
OK, one remaining bug in that was resolved in
https://paste.ubuntu.com/p/sgqJ5dFg5D/. (If there are no matches for
the pattern in the for loop, we still go through it once with the static
string as $disk, which readlink -f doesn't error on.)
Since writing the above, I've realised that we
Oh, except we don't have -e on the readlink in busybox, so I think
https://paste.ubuntu.com/p/sgqJ5dFg5D/ is the winner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872813
Title:
cloud-init
I attempted a fix at https://paste.ubuntu.com/p/hsRgrpr5PT/, but it
appears that /dev/disk/by-path isn't available when the top script runs
at all, so the check never finds any disks. (The existing code that
references those paths appears to be a special case where the script is
running a second
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872813
> This leads to cloud-init can NOT manage network on this VM by default.
Can you describe in a little more detail what problems this is causing
for you? ISO-installed systems generally don't want or need cloud-init
to manage network configuration and I'm trying to understand the use
case here.
On Tue, Apr 14, 2020 at 11:19:53AM -, Naël wrote:
> With the replacement of gnome-software by snap-store in 20.04, this bug
> is no longer apparent. Only users who manually (re-)install gnome-
> software will see it.
I have an up-to-date focal system and I am still seeing this.
--
You
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
To manage notifications about this bug go to:
lxc info:
config:
core.https_address: '[::]:8443'
core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
-
Not sure why it would make a difference, but just in case, I can also
reproduce this against a local container (rather than a remote one).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
$ lxc info reproducer
Name: reproducer
Location: none
Remote: https://34.76.172.211:8443
Architecture: x86_64
Created: 2020/04/09 21:22 UTC
Status: Running
Type: container
Profiles: default
Pid: 16441
Ips:
eth0: inet10.160.29.12veth12a00fff
eth0: inet6
And I just did a `lxd init --auto` on a fresh EC2 instance and I can
also reproduce it there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs
Will post each as separate comments as the others are long:
# ls -lah /proc/self/fd
total 0
dr-x-- 2 root root 0 Apr 9 21:23 .
dr-xr-xr-x 9 root root 0 Apr 9 21:23 ..
lrwx-- 1 root root 64 Apr 9 21:23 0 -> /dev/pts/4
lrwx-- 1 root root 64 Apr 9 21:23 1 -> /dev/pts/4
lrwx-- 1
Steve, does "the grub install to disk is triggered for both" mean we
should be invoking grub-install twice (once for each target), or do we
have another mechanism that we can hook into to perform the install for
all (available|applicable|...) grub targets?
--
You received this bug notification
Thanks Alasdair, I've added a lxd task.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd]
OK, well, now I know what that button does. (And that it doesn't prompt
for confirmation. :p)
(Marking this Opinion because it might be a bug but I didn't mean to
create this one.)
** Changed in: subiquity (Ubuntu)
Status: New => Opinion
--
You received this bug notification because
Ryan has started work on this, moving to In Progress.
** Changed in: cloud-init
Status: Invalid => Triaged
** Changed in: cloud-init
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Steps to reproduce:
$ lxc launch ubuntu-daily:f reproducer
$ lxc shell reproducer
$ vgs
Expected behaviour:
No output (the behaviour on an EC2 instance with no VGs).
Actual behaviour:
Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
invocation. Parent
Public bug reported:
And, AFAICT, it isn't present in any LVM manpage:
$ zgrep tags /usr/share/man/man*/*lvm*
/usr/share/man/man5/lvm.conf.5.gz:See \fBtags\fP configuration setting
description below.
/usr/share/man/man7/lvmreport.7.gz:Let's display one one more field in addition
("lv_tags" in
Still present in 20191207+dfsg.1-1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853909
Title:
neomutt crashed with SIGSEGV in cmd_parse_expunge()
To manage notifications about this bug go to:
> a.) _is_viable_platform will attempt to log an event even if not on
azure. maybe that shouldnt happen.
Maybe!
> b.) _is_viable_platform will return true even if asset_tag failed, but
/var/lib/waagent/ovf-env.xml existed.
I don't _know_ that this is the reason, but is it possible that the
(Marking this Triaged/Low, as we're talking about cleaning things up,
rather than fixing an issue that we know of, I believe.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868077
Title:
A new
A fix for this bug has landed in cloud-init master:
https://github.com/canonical/cloud-
init/commit/6600c642af3817fe5e0170cb7b4eeac4be3c60eb
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Hey Nick,
Thanks for the bug report. It's not 100% clear to me what the issue
here is, could you break down the steps you take to reproduce this in a
little more detail, please? Also, if you do have access to the system
in its failure state, could you run `cloud-init collect-logs` and attach
Some work is in progress on this here: https://github.com/canonical
/cloud-init/pull/237/
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) =>
I do know that some hardened images intentionally have sshd removed, so
that they cannot be accessed at all after launch. (In such cases, any
changes to instances are performed by deploying new ones, rather than
updating existing ones in-place.)
Being able to use cloud-init to bootstrap such
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866562
Title:
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796987
Title:
snapd should log fully to the journal
To manage notifications about
Thanks Olivier! I've filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1617292
** Bug watch added: Mozilla Bugzilla #1617292
https://bugzilla.mozilla.org/show_bug.cgi?id=1617292
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is being worked in https://code.launchpad.net/~waveform/ssh-import-
id/+git/ssh-import-id/+merge/379351
** Changed in: ssh-import-id (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ssh-import-id (Ubuntu)
Status: Confirmed => In Progress
--
You received
This bug is believed to be fixed in cloud-init in version 20.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
101 - 200 of 1128 matches
Mail list logo
