@Adam, may I ask why you are using exit code 0?
I'm more used to exit code 101 when you want to prevent service restarts for
example. Also, I just test with 101 and it doesn't prevent the installation.
https://manpages.ubuntu.com/manpages/noble/man8/invoke-
rc.d.8.html#status%20codes
--
You rec
You are welcome!
Each Ubuntu release is configured to pull LXD from a specific snap
channel (20.04 -> `4.0/stable`, 22.04 -> `5.0/stable`, 24.04 ->
`5.21/stable`) and then it's left to the admin to manage track
switching.
While `do-release-upgrade` could certainly warn about such conditions,
tryi
@Dan, ah thanks so that confirms why you ran into the missing zpool tool
issue because you were on `4.0/stable` which only supports up to ZFS
2.1.
Assuming you don't want to stay on `5.0/edge`, you can go to
`5.0/stable` or move further ahead onto `5.21/stable`. All those have
support for ZFS 2.2.
@Dan, the 5.0/stable snap has support for ZFS 2.2 which is the version
shipped in Noble's 6.8 kernel. As such, there should be no need to
switch to the 5.0/edge channel. This change landed many months ago and
your snap should have updated automatically, in theory.
Could you share what you get from
Thanks Pedro for going through the verification process! Much
appreciated!
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
[ Impact ]
Users running `do-release-upgrade` in a LXD VM through `lxc exec` have
their session disconnected abruptly as lxd-agent.service is restarted
during the upgrade from Jammy->Noble.
The disconnected user will likely re-enter the VM using another `lxc
I've simplified the testing procedure to not involve a `do-release-
upgrade` because I couldn't get it to use noble-proposed to test the fix
on the destination.
Instead, I'm now testing the lxc exec/shell session is not interrupted
while the lxd-agent-loader package is upgraded to 0.7ubuntu0.1. He
** Merge proposal unlinked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/472928
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078936
Title:
l
** Description changed:
* Problem description:
It is quite easy to accidentally trigger the on-demand installation of
LXD's snap which takes a while. This is something that can, for example,
happen inside a LXD instance where the operator didn't notice the
instance was "entered". Some
Public bug reported:
* Problem description:
It is quite easy to accidentally trigger the on-demand installation of
LXD's snap which takes a while. This is something that can, for example,
happen inside a LXD instance where the operator didn't notice the
instance was "entered". Something:
$ lxc l
** Description changed:
Problem description:
Upgrading lxd-agent-loader package causes a restart of the lxd-
agent.service. This service restart can be problematic when the apt
upgrades are done through a `lxc exec` session as the session gets
killed/disconnected abruptly. This is wha
** Description changed:
+ [ Impact ]
+
+ Users running `do-release-upgrade` in a LXD VM through `lxc exec` have
+ their session disconnected abruptly as lxd-agent.service is restarted
+ during the upgrade from Jammy->Noble.
+
+ The disconnected user will likely re-enter the VM using another `lxc
** Description changed:
Problem description:
Upgrading lxd-agent-loader package causes a restart of the lxd-
agent.service. This service restart can be problematic when the apt
upgrades are done through a `lxc exec` session as the session gets
killed/disconnected abruptly. This is wha
Public bug reported:
Problem description:
Upgrading lxd-agent-loader package causes a restart of the lxd-
agent.service. This service restart can be problematic when the apt
upgrades are done through a `lxc exec` session as the session gets
killed/disconnected abruptly. This is what caused
https:
** Summary changed:
- lxd-agent restart during do-release-upgrade breaking the `lxc exec` connection
+ lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
connection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
```
Reported to LXD upstream in
https://github.com/canonical/lxd/issues/14033
** Affects: lxd-agent-loader (Ubuntu)
Importance: Undecided
Assignee: Simon Déziel (sdeziel)
Status: New
** Changed in: lxd-agent-loader (Ubuntu)
Assignee: (unassigned) => Simon Déziel (sdeziel)
--
This was also reproduced Noble's 6.8 kernel as seen in
https://github.com/canonical/lxd/issues/14025
** Bug watch added: github.com/canonical/lxd/issues #14025
https://github.com/canonical/lxd/issues/14025
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
As reported in https://discourse.ubuntu.com/t/when-an-lxc-command-is-
used-on-a-system-without-lxc-lxd-lxd-is-immediately-installed-should-it-
- be-that-way/46570, is is quite easy to accidentally trigger the on-
+ be-that-way/46570, it is quite easy to accidentally tri
Another way to fix this is to remove the `ssl_dhparam` config option
altogether, https://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_dhparam:
> By default no parameters are set, and therefore DHE ciphers will not be used.
If you desire to offer DHE ciphers for older clients, you can easi
** Tags added: verification-done-focal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1980848
Title:
arc_summary doesn't work with HWE kernel 5.15
To manage notific
I first reproduced the initial issue with zfs-linux 0.8.3-1ubuntu12.17:
$ arc_summary
Traceback (most recent call last):
File "/usr/sbin/arc_summary", line 875, in
main()
File "/usr/sbin/arc_summary", line 826, in main
kstats = get_kstats()
File "/usr/sbin/arc_summary", line 259, i
Public bug reported:
As reported in https://discourse.ubuntu.com/t/when-an-lxc-command-is-
used-on-a-system-without-lxc-lxd-lxd-is-immediately-installed-should-it-
be-that-way/46570, is is quite easy to accidentally trigger the on-
demand installation of LXD's snap which takes a while.
A better b
https://bind9.readthedocs.io/en/v9.18.27/reference.html#namedconf-
statement-automatic-interface-scan is the default enabled feature that
causes bind9 to start the conflicting listener, or at least I think it
is.
I believe this is more a bug with how MAAS configures bind9 than
something LXD could
If I'm reading the issue properly, that 10.37.129.1 address would be
from the newly created `lxdbr0` bridge where LXD wants to setup a
dnsmasq listener.
Now presumably that fails because something in MAAS (bind9?) raced with
it and started a listener on it before dnsmasq got a chance.
IIRC, bind9
Corresponding upstream bug
https://github.com/canonical/pylxd/issues/596.
** Bug watch added: github.com/canonical/pylxd/issues #596
https://github.com/canonical/pylxd/issues/596
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@Orion, /etc/ipa isn't a standard location. I think you'd be better off
either adding a local override in
/etc/apparmor.d/local/usr.sbin.rsyslogd or maybe put the CA file
somewhere under /etc/rsyslog.d/. The later path is already something the
rsyslogd profile allows reading.
--
You received this
Public bug reported:
On Noble, installing `ceph-common` result in one of the .so to be
missing a dependent .so:
```
$ lxc launch ubuntu-daily:24.04 c1
$ lxc shell c1
root@c1:~# apt-get update && apt-get install -Vy ceph-common
...
root@c1:~# dpkg -L ceph-common | grep snap
/usr/lib/x86_64-linux
Maybe your nginx is not using the `.gz` file due to access permission
issue or something like that. Anyway, I'd be surprised for it to be a
package issue as I have the exact same version as you and have no issue.
Feels like an environmental issue to me.
--
You received this bug notification becau
Verification for Noble of linux-image-6.8.0-1007-raspi:
root@ubuntu:~# apt-get dist-upgrade -V -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-
@pinnion, I'm still seeing differing ETags between those 2:
$ wget -qSO /dev/null
https://staging.dashboard.villadeus.com/js/select2.full.min.js.gz 2>&1 | grep
ETag
ETag: "667af11b-520f"
$ wget --compress gzip -qSO /dev/null
https://staging.dashboard.villadeus.com/js/select2.full.min.js 2>&1
@pinnion, I just checked a random asset from your site
(https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1)
and the `gzip` version has a different ETag than the uncompressed one:
$ wget -qSO /dev/null
https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 2>&1 | gre
Public bug reported:
The fact that lxd-installer echoes "Installing LXD snap, please be
patient." to stdout while it `snap install lxd` behind the scene can
confuse version checkers like `snapcraft`:
$ lxc launch ubuntu-minimal-daily:24.10 o1
$ lxc exec o1 -- apt-get update -qq
$ lxc exec o1 -- a
*** This bug is a duplicate of bug 1743592 ***
https://bugs.launchpad.net/bugs/1743592
@Nathan, disabling IPv6 is not a supported configuration, other bug
reports about the same behavior were closed as won't fix, see
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/comments/29
for
I've been running this update on Jammy since 2024-04-18 with no visible
side effect:
$ zgrep -w1 apparmor /var/log/apt/history.log.2.gz
Start-Date: 2024-04-18 12:48:18
Commandline: apt install apparmor/jammy-proposed
Requested-By: sdeziel (1000)
Upgrade: apparmor:amd64 (3.0.4-2ubuntu2.3, 3.0.4-2
** Description changed:
+ [ Impact ]
+
+ On GitHub action runners, if there is an update that causes needrestart to
restart the runner-provisioner.service, the action job will immediately fail.
+ While GitHub seem to have tweaked their image to workaround the issue (see
https://bugs.launchpad.n
Thanks @schopin for also discovering that GitHub folks have apparently
worked around the bug by tweaking needrestart config to not restart the
runner-provisioner unit. https://github.com/schopin-pro/needrestart-
ghaction/actions/runs/9518941463/job/26241023047#step:3:163:
```
# Override container
Thanks @schopin! Looking forward for the SRU to Noble ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067800
Title:
needrestart should avoid restarting runner-provisioner.service
To manage notifi
This -38.38 package fixed our cluster test that required FAN to be
working. Marked as verified, thanks!
# uname -a
Linux n1 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:25:01
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-noble-linux
** Tags added:
*** This bug is a duplicate of bug 2057693 ***
https://bugs.launchpad.net/bugs/2057693
** This bug has been marked a duplicate of bug 2057693
Activating autotrim results in high load average due to uninterruptible
threads
--
You received this bug notification because you are a member of
@hyask, in the main issue description you mentioned the HWE was helping.
Is this still the case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067633
Title:
`lxc` commands returning `Error: Failed
I confirmed the "snapd not seeded" problem to affect Focal and later.
** Changed in: lxd-installer (Ubuntu Focal)
Status: New => Confirmed
** Changed in: lxd-installer (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: lxd-installer (Ubuntu Noble)
Status: New => Confirme
The bug was not completely/properly fixed, especially not in Noble:
```
$ lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3.5; lxc exec c1 -- lxc list
Creating c1
Starting c1
Installing LXD snap, please be patient.
Traceback (most recent call last):
File "", line 1, in
ConnectionResetError: [Er
Public bug reported:
On GitHub action runners, if there is an update that causes needrestart
to restart the runner-provisioner.service, the action job will
immediately fail.
```
Restarting services...
/etc/needrestart/restart.d/systemd-manager
systemctl restart packagekit.service php8.3-fpm.ser
Disabling support for 32bit time caught some by surprise:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2062176
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038582
Title:
Turning COMPAT_32BIT
LXD clusters make use of FAN networks when OVN is deemed inappropriate
or not compatible with the environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063298
Title:
deprecate ubuntu-fan in No
Public bug reported:
Since LP: #2061910, lxd-installer pulls LXD snap from `5.21/stable` for
non LTS Ubuntu versions. This should be improved to pull from
`$LTS/stable/ubuntu-XX.YY` as using a specific branch can be handy if we
need to push an emergency fix to the Ubuntu release specific
channel/b
As I could reproduce the issue I opened
https://github.com/canonical/lxd/issues/13512 to track it.
Thanks Dave for bringing this to our attention.
** Bug watch added: github.com/canonical/lxd/issues #13512
https://github.com/canonical/lxd/issues/13512
** Also affects: lxd via
https://githu
As noted by @tomparrott, `unminimize` should not be triggering `lxd-
installer` as even full Noble images don't have LXD seeded, just the
`lxd-installer` wrapper. This is being tracked in
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905
@philroche, I'm assuming you want the oth
** Summary changed:
- LXD snap no longer seeded in non any images so does not need special handling
in unminimize logic
+ LXD snap no longer seeded in any images so does not need special handling in
unminimize logic
** Description changed:
- The LXD snap is no longer seeded in non minimal imag
Diverting the real script (`/sbin/lxd`) instead of the `usrmerged`
symlink (/usr/sbin/lxd`) one works:
```
root@c1:~# dpkg-divert --add --divert /sbin/lxd.REAL --rename /sbin/lxd
Adding 'local diversion of /sbin/lxd to /sbin/lxd.REAL'
root@c1:~# ln -s /bin/true /sbin/lxd
root@c1:~# ll /sbin/lxd* /
Thanks Phil for pointing out that there is some `dpkg-divert` at play
(https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
server/hooks/01-unminimize.chroot_early?h=ubuntu/noble).
I think the issue is due to the `dpkg-diversion` being done prior to
upgrading the `lxd-installer` package
@tobhe, glad to hear that, I've marked the bug as fix released. Thanks!
** Changed in: lxd (Ubuntu)
Status: Incomplete => 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/2057927
Tit
@Paul or @Tobias, would you be able to provide a bit more information on
your environment in a discourse thread at
https://discourse.ubuntu.com/c/lxd/? That would help us hash out a
reproducer. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@Michael, could you provide which LXD version you are running? The LXD
snap rev you are using (27037) doesn't seem to be the latest available
and we, in theory, have fixed the issue in LXD 5.0/stable so maybe the
fix is just a refresh away.
--
You received this bug notification because you are a
Noble SRU verification:
Download the package from launchpad (not yet published in -proposed):
$ wget https://launchpad.net/ubuntu/+source/lxd-
installer/4ubuntu0.1/+build/28436117/+files/lxd-
installer_4ubuntu0.1_all.deb
$ lxc launch ubuntu-minimal-daily:24.04 u1
$ lxc file push /tmp/lxd-instal
** Description changed:
[ Impact ]
- * If the LXD is not pre-created and/or the primary user isn't member of
- it, lxd-installer will fail to install LXD with a cryptic permission
- denied error.
+ * If the LXD group is not pre-created and/or the primary user isn't
+ member of it, lxd-install
** Description changed:
[ Impact ]
* If the LXD is not pre-created and/or the primary user isn't member of
it, lxd-installer will fail to install LXD with a cryptic permission
denied error.
[ Test Plan ]
Create a test instance:
$ lxc launch ubuntu-minimal-daily:24.04 u1
** Description changed:
+ [ Impact ]
+
+ * If the LXD is not pre-created and/or the primary user isn't member of
+ it, lxd-installer will fail to install LXD with a cryptic permission
+ denied error.
+
+ [ Test Plan ]
+
+ Create a test instance:
+
+ $ lxc launch ubuntu-minimal-daily:24.04 u1
+
Public bug reported:
linux-image-extra-virtual currently depends on linux-image-generic which
depends on too much when you consider it's use in VMs.
linux-image-generic comes with unneeded bits like the Intel/AMD
microcodes, linux-firmware and thermald packages which are most of the
time unneeded
** Changed in: lxd (Ubuntu)
Status: Incomplete => Confirmed
** Bug watch added: github.com/canonical/lxd/issues #13420
https://github.com/canonical/lxd/issues/13420
** Also affects: lxd via
https://github.com/canonical/lxd/issues/13420
Importance: Unknown
Status: Unknown
-
Here's how to reproduce this in a LXD VM:
Download Ubuntu 24.04 Desktop image into ~/Downloads
Import the ISO
$ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso
24.04-desktop --type=iso
Prepare a LXD VM
$ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c l
@sergiodj, it's not a proper SRU/MRE verification but this
5.9-0ubuntu0.22.04.1 is running fine on my home lab. If I run into any
problem with it, I'll report back here. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
*** This bug is a duplicate of bug 2060676 ***
https://bugs.launchpad.net/bugs/2060676
** This bug has been marked a duplicate of bug 2060676
login: remove pam_lastlog.so from config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I just tested 5.21/stable and couldn't reproduce as it properly disable
the /proc/sys/kernel/apparmor_restrict_unprivileged_userns and
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined that would
otherwise have caused those denials.
Marking as incomplete until you can reproduce with 5.21/
@Bartosz it seems you were lucky with 24GB ends being with a multiple of
16KiB (ZFS uses K and G to mean KiB and GiB btw):
$ lxc config device override testvm root size=24GB
Device root overridden for testvm
$ zfs get -p volsize default/virtual-machines/testvm.block
NAME
Lena, thanks for that MRE! It passes some operational tests on my own
setup: primary/secondaries with TSIG, some with views, some zones with
inline DNSSEC signing and with RFC 7706/8806 local root zone copy.
I only tested with Jammy hosts so with 1:9.18.24-0ubuntu0.22.04.1
--
You received this b
Thanks for the follow-up!
** Changed in: lxc (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/2060965
Title:
liblxc is missing in 24.04
To manage notificat
> The one performance improvement (that I didn't benchmark): "Make
compression libraries dynamically loadable" (it's from January, not
April).
Should apparently make the initialization quicker. Nice to see this
coming from a reputable source (@redhat.com) ;)
--
You received this bug notification
Public bug reported:
If `lxd-installer` cannot figure which LXD snap channel to use, it
currently defaults to pulling from `latest/stable`. `latest/stable` is a
moving target as new LXD versions are pushed to it on a monthly basis.
`lxd-installer`'s target audience are those casually running `lxc`
Marking as fix released as it was included in snapd 2.62, thanks!
** Changed in: snapd (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/2046379
Title:
snapd
The problem is not with a Raspberry Pi as that works fine:
ubuntu@ubuntu:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu Noble Numbat (development branch)"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.c
@enr0n, could you share `snap changes` as well as `snap info lxd`,
please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061017
Title:
lxd-installer: permission error not handled and lxd snap not i
Thank you both!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053192
Title:
geoipupdate should be moved to universe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
The telepathy-haze package is no longer shipped in the archives. It's
not in Focal which is the oldest supported release. Marking as
incomplete for autoclosing in a few days.
** Changed in: telepathy-haze (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification becau
libgnomeprint is no longer shipped in the archive after Precise, as
such, marking as incomplete (can't mark as won't fix) for autoclose in a
few days.
** Changed in: libgnomeprint (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058303
Title:
lxd
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-loader/+git/lxd-agent-loader/+merge/463175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058302
Title:
lxd
Public bug reported:
When the host uses a manually compiled LXD where binaries were not
stripped, the `lxd-agent` can be ~31MiB big. This binary is copied
inside the VM guest when the VM boots up. This copy operation can fail
as the tmpfs in the VM is mounted with `size=25MiB`.
This binary is the
Public bug reported:
This was originally reported at https://github.com/lxc/incus/issues/484
which is recopied here (s/incus/lxd/):
On Red Hat based VMs using SELinux, we seem to be occasionally hitting
lxd-agent startup issues due to systemd not being able to execute the
agent binary.
This is b
Thanks Dan, that prompted me to also call out that's something that
manifests only on distro upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd-agent-setup cannot be started a
** Summary changed:
- lxd-agent-setup cannot be started
+ lxd-agent-setup cannot be started after a distro upgrade to 24.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054814
Title:
lxd-agent-se
https://github.com/canonical/cloud-init/pull/4970 contains a proposed
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055219
Title:
`zpool status` called even if not installed in a container
To
Public bug reported:
It seems that cloud-init tries to use `zpool status ` whenever
`/dev/zfs` exists. This can causes some bogus warnings if the zpool
command it not available despite that `/dev/zfs` existing.
Here is how to reproduce:
```
lxc launch ubuntu-daily:22.04 v1 --vm
sleep 30
lxc exec
The workaround from #71 worked almost perfectly out of the box, I've
only seen 1-2 windows staying under the dock. I probably simply need
bump the delay a bit from the default value.
Thanks a lot @popov895. @ballogy, thanks for working on this with
upstream!
--
You received this bug notification
@enr0n, yes, I did restart systemd-networkd after creating
/etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf.
If you want to reproduce, the steps outlined in the bug descriptions
should provide you with a simple reproducer.
--
You received this bug notification because you are a m
@enr0n, the proposal to add:
bridges:
br0:
interfaces: [vlan1]
To the network config defeats the purpose. The goal is to not have to do
double configuration. The bridge is define in LXD, the vlan1 only in
netplan.
The other proposed fix of `KeepMaster=true` snippet in
/etc/systemd/network/
I got the initial assessment wrong, thanks Heinrich for clearing up that
confusion :)
Here is what happened here:
On Jammy, lxd-agent-loader (0.5) is configured to start lxd-agent.service when
the multi-user.target was reached coupled with a
ConditionPathExists=/dev/virtio-ports/org.linuxconta
This was fixed in ca-certificates version 20211016 which is what Jammy
released with. As of today, all Ubuntu releases from Bionic onward ship
20230311 so marking as fix released.
** Changed in: ca-certificates (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
Nowadays, btrfs snapshots can only be taken by the owner of the source
subvol. https://btrfs.readthedocs.io/en/latest/ch-mount-
options.html#btrfs-specific-mount-options:
> Historically, any user could create a snapshot even if he was not
owner of the source subvolume, the subvolume deletion has b
@kip, it seems the problem was merely a configuration issue on your
machine (missing SSL cert file), not a bug in NGINX or NGINX's package.
As such, we probably don't need to look further into your logs but if
you want to take a look, they should still be available for you to
consult with `journalc
@kip, it should in theory not have crashed the installer. Only the
nginx(-*) package(s) should be left unconfigured. You can check that
with "dpkg -l | grep -v ^ii", it should show you which packages need
attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
MySQL 5.1 has long been EOL in Ubuntu and upstream. Please open a new
bug if MySQL 5.7 or MySQL 8.0 as shipped in currently supported Ubuntu
version still have the problem.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification becau
This has long been fixed.
** Changed in: mysql-dfsg-5.1 (Ubuntu)
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/779670
Title:
The usage of --defaults-file is
@Jan, indeed before replying to you I opened
https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1970440 ;)
@Paul, I am assuming you are referring to the "not well maintained" part
of my comment so let me clarify. Ubuntu being a "frozen distro" (package
versions are normally set in stone at r
Hello Holbok,
It looks like your system is booted with `ipv6.disable=1`:
Apr 26 08:28:53 kvmf kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-109-generic
root=UUID=a5928baa-1a87-4f79-88a2-eab3489fdea1 ro net.ifnames=0
biosdevname=0 ipv6.disable=1 maybe-ubiquity ipv6.disable=1
Whic
@Jan, while I understand the convenience of `apt install`, Wordpress is
unfortunately not well maintained in Ubuntu so I would recommend doing a
manual installation of an upstream supported version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@ubuntu-archive, would it be possible to add `wordpress` the sync
blocklist/blacklist, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970440
Title:
wordpress should be removed from the archi
Public bug reported:
The just released Ubuntu 22.04 ships with wordpress 5.8.3 which is
already outdated as 5.8.4 was released addressing 1 bug and 3 security
problems, see https://wordpress.org/support/wordpress-
version/version-5-8-4/#maintenance-updates
It seems that nobody from the community
Looks like the missing bits were re-added in Bionic HWE kernel version
5.4.0-108.122~18.04.1. This allowed confirming with the recently
released -109 version:
root@bionic-vm:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@bionic-vm:~# uname -a
Linux bionic-vm 5.4.0
1 - 100 of 2170 matches
Mail list logo
