Hi Aman,
Thanks for the bug report! Configuring the FQDN to point at the
loopback address has been cloud-init's behaviour since 2011 on Ubuntu
(https://github.com/canonical/cloud-
init/commit/6d25c040ee566f6ef85352d7b52eb5947230f78a) and 2012 on Red
Hat (https://github.com/canonical/cloud-
init/c
Public bug reported:
The system was restored from hibernation this morning, but the issue did
not exhibit for ~30 minutes after "boot". I have also seen hard locks
without hibernation (but they have never produced any journal output, so
may be a different issue). Examining `journalctl -k`, I see
Looking through the journal further, I do see non-NVidia call traces
such as:
Nov 27 09:43:52 surprise kernel: INFO: task qemu-system-x86:16736 blocked for
more than 120 seconds.
Nov 27 09:43:52 surprise kernel: Tainted: P OEL
5.8.0-29-generic #31-Ubuntu
Nov 27 09:43:52 surpri
** 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/1906187
Title:
Ver
Hi Ian,
I've just launched such a container and I see a bunch of non-cloud-init
errors in the log and when I examine `systemctl list-jobs`, I see that
the two running jobs are systemd-logind.service and
snapd.seeded.service:
root@certain-cod:~# systemctl list-jobs
JOB UNIT
I've figured out why my LXD reproducer doesn't reproduce exactly:
NoCloud runs at both local and net stages, so the code in question is
called earlier in boot than the OpenStack data source is. For now, I'll
proceed with the synthetic reproducer: calling the Python code which
fails directly.
--
Hey Frode,
Now moving on from the "does this system have any OVS-managed
interfaces?" to "how can I tell if a particular interface is managed by
OVS?":
We discussed using `udevadm info` to determine if an interface is OVS-
managed:
> If it is sufficient to know that this is a Open vSwitch manage
To ensure that we understand the consequences of these changes, I've
spent a bit of time tracking down everywhere this will affect in cloud-
init by looking up the various call chains of `get_interfaces`:
Called by:
* `_get_current_rename_info`
* `_rename_interfaces`
* `apply_network_config_
> But I guess it would be reasonable to split the work up in bite sized
chunks as long as we allow for supporting this in the design.
Having looked a little more, I don't think an incremental approach buys
us much here: we'd have to replace the `udevadm` code with `ovs-vsctl`
code in the next stag
Another question: is there a canonical way to determine if OVS isn't up?
Currently I'm trying to execute a command and looking for "database
connection failed" in the output, is that appropriate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> Interfaces of type 'internal' may be used for other things than VLANs
so depending on what you want to match on it may or may not be precise
enough.
So the cloud-init code in question is used in a couple of (relevant)
ways: (a) to determine the state of any physical interfaces for which we
shoul
For hirsute, the bug does not reproduce on upgrade from the release day
image. However, it can present when upgrading between releases.
To test, I launched a groovy instance with an old cloud-init (the same
image as previously for groovy validation).
I performed a `do-release-upgrade -d` (-d, as
Public bug reported:
To quote:
# AUTOCHECK:
# should mdadm run periodic redundancy checks over your arrays? See
# /etc/cron.d/mdadm.
AUTOCHECK=true
# AUTOSCAN:
# should mdadm check once a day for degraded arrays? See
# /etc/cron.daily/mdadm.
AUTOSCAN=true
Neither /etc/cron.d/mdadm nor /
I'm performing verification of this locally using the cloud-init
integration testing framework. Specifically, I'm running
test_upgrade_package[0] with the following diff applied (to trigger this
bug):
@@ -104,18 +104,19 @@ def test_upgrade(session_cloud: IntegrationCloud):
@pytest.mark.ci
@py
For groovy, I'm testing with the `ubuntu:bac1692e9ec7` image, with a
serial of 20201210. First, I confirm that the test does trigger the bug
on UPGRADE to the version of cloud-init in the release:
$ CLOUD_INIT_OS_IMAGE=ubuntu:bac1692e9ec7::ubuntu::groovy
CLOUD_INIT_CLOUD_INIT_SOURCE=UPGRADE pyte
For focal, I'm performing the same process but with the
`ubuntu:b321e3832dbb` image, serial of 20201210.
UPGRADE does fail:
$ CLOUD_INIT_OS_IMAGE=ubuntu:b321e3832dbb::ubuntu::focal
CLOUD_INIT_CLOUD_INIT_SOURCE=UPGRADE pytest
tests/integration_tests/test_upgrade.py::test_subsequent_boot_of_upgra
For bionic, I'm performing the same process but with the
`ubuntu:c2bdb694ecc2` image, serial of 20201211.1.
UPGRADE does fail:
$ CLOUD_INIT_OS_IMAGE=ubuntu:c2bdb694ecc2::ubuntu::bionic
CLOUD_INIT_CLOUD_INIT_SOURCE=UPGRADE pytest
tests/integration_tests/test_upgrade.py::test_subsequent_boot_of_u
For xenial, I'm performing the same process but with the
`ubuntu:bb8e87956495` image, serial of 20201210.
UPGRADE does fail:
$ CLOUD_INIT_OS_IMAGE=ubuntu:bb8e87956495::ubuntu::xenial
CLOUD_INIT_CLOUD_INIT_SOURCE=UPGRADE pytest
tests/integration_tests/test_upgrade.py::test_subsequent_boot_of_upg
An alternative explanation: Azure has a pre-provisioning system, whereby
they'll partially boot a machine and then hold it in that state until a
user requests a system which corresponds. This is implemented using the
netlink socket you see: the fabric will reconnect that socket once it is
ready fo
In the cloud-init log, I see:
2021-04-19 06:58:24,455 - stages.py[DEBUG]: applying net config names for
{'version': 2, 'ethernets': {'eth0': {'match': {'driver': 'bcmgenet smsc95xx
lan78xx'}, 'set-name': 'eth0', 'dhcp4': True, 'optional': True}}}
2021-04-19 06:58:24,456 - __init__.py[DEBUG]: no
Hi Kai-Heng,
Here is the (much longer) trace from that kernel.
Thanks!
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:442
dev_watchdog+0x24c/0x250
kernel: Modules linked
Hey folks,
Thanks for the report! If someone could run `cloud-init collect-logs`
on an affected instance, and upload the produced tarball to this bug, we
can dig into it further. The contents of /etc/netplan would also be
very handy.
(Once attached, please move this back to New.)
Cheers,
Dan
When investigating another issue, I found this line in my journal,
repeated a few times:
nm-dispatcher[3938]: /etc/network/if-up.d/resolved: 12: mystatedir: not
found
Not sure if that's related, but it seems suspicious at least.
--
You received this bug notification because you are a member of
OK, I've managed to reproduce this (in a non-Juju launched VM). The
ordering of these journal lines look suspicious to me:
Nov 09 17:41:51.091033 ubuntu systemd[1]: Starting udev Coldplug all Devices...
Nov 09 17:41:51.236309 ubuntu systemd[1]: Finished Load Kernel Modules.
Nov 09 17:41:51.363482
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902960
Title:
Upgrad
Hi yhzou,
Thanks for using (and testing!) Ubuntu, and for filing this bug.
Setting a default password in the cloud-images.ubuntu.com images would
make them insecure: any Ubuntu instance launched from them would have a
backdoor installed, essentially.
There are a couple of options: you could speci
Thanks for the explanation, Dan! I was off down a wrong path, I
appreciate the correction.
I've just downloaded the Azure image from cloud-images.u.c and it
includes this in `/etc/netplan/90-hotplug-azure.yaml`:
# This netplan yaml is delivered in Azure cloud images to support
# attaching and de
(Added cloud-images for visibility.)
** Also affects: cloud-images
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/1902960
Title:
Upgrade from 245.4-4ubunt
I've just tested, and this doesn't seem to reproduce when launching from
a captured image (with 90-hotplug-azure.yaml restored and `cloud-init
clean` executed). So I think I've exhausted the ways in which I can
attempt to gain more insight into what's happening during the part of
boot where this r
Trace from that mainline kernel:
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:442
dev_watchdog+0x24c/0x250
kernel: Modules linked in: scsi_transport_iscsi binfmt_misc veth
The attached are the logs of a curtin run with the -proposed cloud-init.
The only "failures", indicate that expected-to-fail tests instead passed
(because the underlying issues have since been addressed in Ubuntu).
** Attachment added: "curtin verification testing logs"
https://bugs.launchpad.
** Attachment added: "Verification logs for KVM"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599/+attachment/5444544/+files/nocloud-nocloud-kvm-sru-20.4.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "Verification logs for LXD"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599/+attachment/5444543/+files/nocloud-lxd-sru-20.4.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Changed in: livecd-rootfs (Ubuntu Xenial)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776706
Title:
clean_loops can't be called multiple times with set -u
To man
Public bug reported:
This file was previously shipped by walinuxagent to unambiguously
configure cloud-init to use the Azure data source. It is no longer
present in the latest version in disco, or the versions in
{trusty,xenial,bionic,cosmic}-proposed.
This file should be restored, so that cloud
Microsoft's testing has turned up
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1806972 as
an issue in the latest version of walinuxagent, which will need
addressing before we can SRU it.
** Tags removed: verification-needed-bionic verification-needed-cosmic
verification-needed-trus
http://cloud-images.ubuntu.com/cosmic/20180906/unpacked/cosmic-
daily.changelog outlines the changed packages between the two images. I
strongly suspect that the root cause of this is the systemd environment
generator added in the latest version of snapd, so I've added snapd to
this bug.
The chan
Public bug reported:
>From time-to-time, when using cosmic, my keyboard presses will no longer
register. This applies to both the internal laptop keyboard and my
external keyboard. I haven't identified any particular trigger of this.
The one workaround I have found is to use the mouse (which is
Is there anything specific that I can do to capture more information
when this happens again? Browsing through the systemd journal didn't
reveal anything obvious, but I don't necessarily know what to look for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
I use more than one browser profile, only one of which is logged in to
Launchpad. When using ubuntu-bug to report a bug, it will open the page
in whichever one happened to be focused last. If this browser profile
isn't logged in to Launchpad, it will redirect me to a login p
On Fri, Oct 12, 2018 at 07:18:51AM -, Georgi Georgiev wrote:
> Any reason why the executable bit of diff-highlight is stripped?
>
> If I run `sudo make -B -C /usr/share/doc/git/contrib/diff-highlight
> diff-highlight` the generated file is executable, but the one shipped
> with the package is
** Changed in: livecd-rootfs (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/1797170
Title:
xenial cloud image builds fail due to /lib/modules being
Hi John,
I've just tested with the latest Vagrant box, and this looks good to me
now:
$ vagrant box update
==> default: Checking for updates to 'ubuntu/cosmic64'
default: Latest installed version: 20181008.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: U
On Tue, Oct 16, 2018 at 12:20:21PM -, John Patrick wrote:
> Cheers all,
> Just updated myself and picked up '20181015.0.0' and vagrant up works cleanly.
> John
Great, thanks for the confirmation!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: cloud-images
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/1726818
Title:
vagrant artful64 box filesystem too small
To manage notifications a
This is now fixed.
** Changed in: cloud-images
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/1585233
Title:
Provide -root.tar.xz for bionic and later
To ma
I was able to SSH in before the service completed, so I don't think it's
just a lack of network connectivity.
http://paste.ubuntu.com/p/pSrJJVD8zt/ is the full journalctl output from
the (GCE) instance.
(I'm not 100% sure if this is relevant to the second part of your
comment, Dimitri, but this i
** Description changed:
+ In bionic, the vboxsf module was included in linux-modules-...-generic:
+
+ $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep
vboxsf.ko
+ -rw-r--r-- root/root 63238 2018-09-24 10:08
./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vbo
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199144/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
Title:
Shar
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199148/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/179
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199147/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199149/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199145/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17966
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199146/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 9 16:18 seq
crw-rw 1 root audio 116, 33 Oct 9 16:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199143/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199150/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796647
Title:
Sh
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1796647/+attachment/5199151/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
My understanding of the issue after an IRC conversation with sforshee is
that the modules were intentionally dropped from the kernel packages,
but the corresponding Provides of virtualbox-guest-modules was _not_
dropped from the kernel packaging. This means that when we install
virtualbox-guest-ut
This is from a cosmic GCE instance _before_ the lxd snap was seeded
(i.e. with just the google-cloud-sdk snap seeded):
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" charact
This is from a cosmic GCE instance _after_ the lxd snap has been seeded:
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @23.527s
└─multi-user.ta
As requested on IRC:
$ systemctl cat snap.lxd.daemon.unix.socket
# /etc/systemd/system/snap.lxd.daemon.unix.socket
[Unit]
# Auto-generated, DO NOT EDIT
Description=Socket unix for snap application lxd.daemon
Requires=snap-lxd-9010.mount
After=snap-lxd-9010.mount
X-Snappy=yes
[Socket]
Service=snap
http://people.canonical.com/~dwatkins/1796137.svg is a `systemd-analyze
plot` run on the instance with lxd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796137
Title:
huge and slow image 20181002
Some more details about what's happening inside snapd:
$ snap changes --abs-time
ID Status Spawn Ready Summary
1Done2018-10-09T20:35:36Z 2018-10-09T20:35:47Z Initialize system state
2Done2018-10-09T20:35:36Z 2018-10-09T20:35:38Z Initialize dev
The box certainly needs to be fixed.
(In the meantime, a workaround if you _really_ need a cosmic box is
probably to manually install the virtualbox-guest-dkms package; I
haven't tested this locally though.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Currently, one has to run (multiple) snap commands to get the "logs" of
what snapd has done on a system. This is not only annoying (because the
commands one has to run are dynamic based on change IDs, so it requires
scripting), but also means that normal methods of collating
Further to this, I believe snapd drops its record of old changes at some
point, with no way of understanding what happened before its oldest
recorded change. If these changes were logged, regular log
rotation/retention would retain this information.
--
You received this bug notification because
>From a pre-LXD-seeding instance, the plot is at
http://people.canonical.com/~dwatkins/1796137-before.svg and the `snap
change` output is:
$ snap change --abs-time 1
Status Spawn Ready Summary
Done2018-10-09T20:41:32Z 2018-10-09T20:41:33Z Ensure prerequisites
build of the ubuntu-cpc project; it will fail without a
fix, and pass with a fix.
[Regression Potential]
The fix is to modify the `mkdir` to `mkdir -p`, so the potential for
regression is very low.
** Affects: livecd-rootfs (Ubuntu)
Importance: Critical
Assignee: Dan Watkins (daniel
: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => 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/1797170
Title:
xenial cloud im
** Tags added: verification-needed-bionic verification-needed-cosmic
verification-needed-trusty verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799498
Title:
New Microsoft
Public bug reported:
As you can see here:
```
$ head -n3 /usr/share/apport/package-hooks/source_gnome-screensaver.py
ubuntu/devel [ 17:38:44 ]
+#!/usr/bin/python
+
'''Apport package hook for gnome-
Public bug reported:
Even once bug 1804709 is addressed and the hook can run at all, it still
won't work on default Ubuntu installations (which don't have Python 2)
because the shebang points at /usr/bin/python.
** Affects: gnome-screenshot (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
$ sudo apt-get remove -y sendmail-base
100 [ 09:37:15 ]
Reading package lists... Done
Building dependency tree
Readin
** Changed in: cloud-images
Status: New => Confirmed
** Also affects: livecd-rootfs (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/1787506
T
I can also confirm that installing linux-modules-extra-5.0.0-8-generic
(which also pulls in crda iw libnl-genl-3-200 wireless-regdb) caused
this problem to no longer appear.
(I'm happy for this to be marked duplicate, but I wonder if there's
still an iptables bug, given that memory allocation is p
Public bug reported:
Filing this so that we have a bug that can be tagged block-proposed to
be very sure we don't accidentally migrate before testing is complete.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Tags: block-proposed
--
You received this bug n
Please find attached a debdiff for the latest version of probert.
** Patch added: "probert.debdiff"
https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1821994/+attachment/5254771/+files/probert.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This just happened again (on 73.0+build3-0ubuntu1) and I've noticed that
the issue appears to apply _per window_. So if I launch Firefox and
this is happening, then I can open a new window and, provided I don't
open any websites, the menus function correctly (to allow me to disable
Strict tracking
OK, this (or at least some part of it) finally reproduced on an upstream
kernel (5.4.19-050419-generic)! I've attached the journal from "[ cut
here ]" onwards, with some minor redaction of VPN endpoints.
** Attachment added: "5.4.19-050419-generic.journal.txt"
https://bugs.launchpad.net/ubunt
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
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
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
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 t
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.
htt
** 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 t
Jamie, are you using an ISO install or a cloud image for your test? I
was seeing this in a cloud image.
(When we were debugging on IRC, I recall that being a difference that
meant people couldn't reproduce.)
** Changed in: iptables (Ubuntu)
Status: Incomplete => New
--
You received this
Public bug reported:
For 19.04, we would like to expand the support for block device
discovery available in curtin, to support installation on to existing
partition in subiquity. The curtin changes will be covered under its
standing FFE[0], but they will introduce a dependency on new probert
func
** Description changed:
On the extended testing for the SRU in bug 1817665 we found that there
are a few dependency issues that need to be fixed.
Affects X&T:
python-libnacl - depends on <1.4 but xenial (and trusty soon) have 1.4.5
Fix by importing
https://github.com/ecordell/pymacar
Chad, I think those are all symptoms of the underlying issue: the
network configuration was generated just fine on first boot, but on a
subsequent boot with a different NIC, it no longer applies.
I'm going to mark this as Triaged/Wishlist because cloud-init is
behaving as intended, but we would (s
Dropped the Ubuntu tasks as (IIUC) the code that caused this problem
isn't in the Ubuntu package, we're only seeing it because subiquity
is/was consuming curtin master.
** Changed in: curtin
Status: New => Fix Committed
** Changed in: curtin
Assignee: (unassigned) => Michael Hudson-Do
(Dropped the curtin task so we're only tracking status in one place for
now.)
Ryan, is this really Incomplete given "Curtin should stop installing
kernel-img.conf for Eoan and later" is in the bug description?
** No longer affects: curtin
--
You received this bug notification because you are a
(I'm dropping the curtin task from this for now, while the subiquity
folks triage it. If it turns out to need curtin work, please do add it
back!)
** No longer affects: curtin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I started seeing this when I booted this morning, and I've seen it in
the 2 reboots since (one for a new kernel, one to capture debug logs).
After modifying /etc/udev/udev.conf to capture debug logging, I see:
$ journalctl -u systemd-udev-settle.service -b0
-- Logs begin at W
Public bug reported:
I'm currently debugging something based on journal output. I,
helpfully, know what kernel was running due to this line:
kernel: Linux version 5.3.0-13-generic (buildd@lgw01-amd64-012) (gcc
version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #14-Ubuntu SMP Tue Sep
24 02:46:08 U
I just did a purge of apt-file and reinstalled (on eoan), and I'm still
seeing the same issue. (The config file installed was identical to the
one from before the purge.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
A fix for this bug was committed to cloud-init master in
https://github.com/canonical/cloud-
init/commit/28aa8c5a16b67ea0226734eeadfa2c467701899d
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Ryan Harper (r
On Mon, Jan 27, 2020 at 05:07:06PM -, Colin Ian King wrote:
> I guess the next question is why dmidecode being run as root is required
> on a cloud init?
cloud-init uses DMI data to identify that it is running on certain
platforms. It will use /sys/class/dmi/... if available, but falls back
t
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
A fix for this landed in cloud-init master here:
https://github.com/canonical/cloud-
init/commit/2bedc44092ec94faebfb2f55c6d7c6bdd754df23
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
1 - 100 of 1034 matches
Mail list logo
