[Bug 1531964] Re: Unable to unlock cryptsetup with external keyboard when using MODULES=dep

[Simon Déziel]

Unfortunately, this is still an issue on Jammy:

$ lsb_release -rd
Description:Ubuntu 22.04.5 LTS
Release:22.04

$ apt-cache policy initramfs-tools linux-image-generic-hwe-22.04
initramfs-tools:
  Installed: 0.140ubuntu13.5
  Candidate: 0.140ubuntu13.5
  Version table:
 *** 0.140ubuntu13.5 100
100 /var/lib/dpkg/status
 0.140ubuntu13.4 500
500 https://apt.sdeziel.info/archive/ubuntu jammy-updates/main amd64 
Packages
 0.140ubuntu13 500
500 https://apt.sdeziel.info/archive/ubuntu jammy/main amd64 Packages
linux-image-generic-hwe-22.04:
  Installed: 6.8.0-45.45~22.04.1
  Candidate: 6.8.0-45.45~22.04.1
  Version table:
 *** 6.8.0-45.45~22.04.1 500
500 https://apt.sdeziel.info/archive/ubuntu jammy-updates/main amd64 
Packages
500 https://apt.sdeziel.info/security/ubuntu jammy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 5.15.0.25.27 500
500 https://apt.sdeziel.info/archive/ubuntu jammy/main amd64 Packages

$ cat /etc/initramfs-tools/conf.d/modules.conf 
# File managed by Puppet
MODULES=dep

$ grep -v ^# /etc/initramfs-tools/modules 
hid
hid_generic
usbhid
xxhash_generic

Without the hid related modules, I cannot use my external keyboard to
unlock my cryptsetup.


** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531964

Title:
  Unable to unlock cryptsetup with external keyboard when using
  MODULES=dep

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1531964/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597017] Re: mount rules grant excessive permissions

[Simon Déziel]

@Andrew, I think publishing to -updates first and then to -security was
intentional per https://discourse.ubuntu.com/t/upcoming-apparmor-
security-update-for-cve-2016-1585/44268/3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597017

Title:
  mount rules grant excessive permissions

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1597017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073318] Re: Backport of openvpn for jammy and noble

[Simon Déziel]

The jammy -proposed package (2.5.11-0ubuntu0.22.04.1) tested fine here:

```
...
Suggested packages:
   resolvconf (1.84ubuntu1)
   openvpn-systemd-resolved (1.3.0-3.1)
   easy-rsa (3.0.8-1ubuntu1)
The following packages will be upgraded:
   openvpn (2.5.9-0ubuntu0.22.04.3 => 2.5.11-0ubuntu0.22.04.1)
1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
Need to get 0 B/619 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
...
```

It was only mildly tested but it allows connecting to Canonical corp VPN
at least. This was tested through the NM openvpn plugin.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073318

Title:
  Backport of openvpn for jammy and noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/2073318/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 575542] Re: resize2fs does not respect flex_bg

[Simon Déziel]

Marking as fix released per comment #4 saying that e2fsprogs 1.44+
contained the fix. This means Bionic onward.

** Changed in: e2fsprogs (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/575542

Title:
  resize2fs does not respect flex_bg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/575542/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages

[Simon Déziel]

As Russell pointed out this sounds like the issue we had with lxd-agent-
loader (since fixed) as virtiofs and 9pnet-virtio are both exercised by
it. I'll mark the bug as incomplete for now.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055310

Title:
  dmesg spammed by virtui-fs and 9pnet-virtio messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2081308] Re: open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)

[Simon Déziel]

Here's a simple way to reproduce the issue (assuming you have LXD
installed):

```
lxc launch ubuntu-daily:24.04 n1
echo "exit 0" | lxc exec n1 -- tee /usr/sbin/policy-rc.d
lxc exec n1 -- chmod +x /usr/sbin/policy-rc.d

lxc exec n1 -- apt-get update -qq
lxc exec n1 -- apt-get install -y nginx

lxc shell n1
```

And once inside `n1`, to learn more about where it fails during
postinst:

```
sed -i 's|set -e|set -ex|' /var/lib/dpkg/info/nginx.postinst
apt-get install -f
```

Will give this:

```
Setting up nginx (1.24.0-2ubuntu7.1) ...
+ invoke-rc.d --quiet nginx status
+ ss -nlt sport = 80
+ grep -v ^State
+ [ -z  ]
+ invoke-rc.d nginx start
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for 
details.
invoke-rc.d: initscript nginx, action "start" failed.
× nginx.service - A high performance web server and a reverse proxy server
 Loaded: loaded (/usr/lib/systemd/system/nginx.service; disabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Fri 2024-09-20 18:29:38 UTC; 6ms 
ago
   Docs: man:nginx(8)
Process: 1404 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; 
master_process on; (code=exited, status=1/FAILURE)
CPU: 2ms

Sep 20 18:29:38 n1 systemd[1]: Starting nginx.service - A high performance web 
server and a reverse proxy server...
Sep 20 18:29:38 n1 nginx[1404]: 2024/09/20 18:29:38 [emerg] 1404#1404: open() 
"/etc/nginx/nginx.conf" failed (2: No such file or directory)
Sep 20 18:29:38 n1 nginx[1404]: nginx: configuration file /etc/nginx/nginx.conf 
test failed
Sep 20 18:29:38 n1 systemd[1]: nginx.service: Control process exited, 
code=exited, status=1/FAILURE
Sep 20 18:29:38 n1 systemd[1]: nginx.service: Failed with result 'exit-code'.
Sep 20 18:29:38 n1 systemd[1]: Failed to start nginx.service - A high 
performance web server and a reverse proxy server.
+ exit 1
```

So `invoke-rc.d nginx start` tries to start (apparently intentional
based on Adam's interpretation of exit code 0) but that is tried before
the file `/etc/nginx/nginx.conf` is created. Only
`/etc/nginx/nginx.conf.dpkg-new` exist at that point.

It's not clear to me why only the `.dpkg-new` file exist but maybe
that's due to the split between `nginx` and `nginx-common` as teward
mentioned (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082373)?
Trying to install just `nginx-common` doesn't work as that automatically
pulls in `nginx` :/

** Bug watch added: Debian Bug tracker #1082373
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082373

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308

Title:
  open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2081308] Re: open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)

[Simon Déziel]

@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 received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308

Title:
  open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2081308/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080888] Re: LXD 4.0 fails to start on kernel 6.8 with message: "Required tool 'zpool' is missing"

[Simon Déziel]

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,
trying to automatically do the switching might be risky. The warning
though makes a lot of sense to me, thanks for suggesting it!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080888

Title:
  LXD 4.0 fails to start on kernel 6.8 with message: "Required tool
  'zpool' is missing"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2080888/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080888] Re: LXD fails to start with message: "Required tool 'zpool' is missing"

[Simon Déziel]

@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. You can check their respective end of life here:
https://documentation.ubuntu.com/lxd/en/latest/support/

** Summary changed:

- LXD fails to start with message: "Required tool 'zpool' is missing"
+ LXD 4.0 fails to start on kernel 6.8 with message: "Required tool 'zpool' is 
missing"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080888

Title:
  LXD 4.0 fails to start on kernel 6.8 with message: "Required tool
  'zpool' is missing"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2080888/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080888] Re: LXD fails to start with message: "Required tool 'zpool' is missing"

[Simon Déziel]

@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: `snap list --all lxd`


With that said, now that you are on Noble, you can probably think about 
switching from the old LXD LTS (5.0) to the new one (5.21) that came along with 
Noble. To switch: `sudo snap refresh lxd --channel 5.21/stable`. Just be 
mindful that's a one way switch as you won't be able to go back to 5.0.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080888

Title:
  LXD fails to start with message: "Required tool 'zpool' is missing"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2080888/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

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 Ubuntu.
https://bugs.launchpad.net/bugs/2078936

Title:
  lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

** 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
  exec` but might be confused by the `do-release-upgrade` command still
  running but being hard to re-attach.
  
  The upload would fix this disconnect problem by simply not stopping the
  `lxd-agent.service` on package upgrade.
  
  [ Test Plan ]
  
  How to reproduce the bug:
  
  ```
  $ lxc launch ubuntu-minimal-daily:24.04 v1 --vm
  $ lxc shell v1
  # now inside the VM, enable noble-proposed
- root@v1:~# sed -i 's/noble-backports$/noble-proposed/' 
/etc/apt/sources.list.d/# ubuntu.sources
+ root@v1:~# sed -i 's/noble-backports$/noble-proposed/' 
/etc/apt/sources.list.d/ubuntu.sources
  root@v1:~# apt-get update
  
  # install lxd-agent-loader from noble-proposed
  root@v1:~# apt-get install lxd-agent-loader -t noble-proposed
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be upgraded:
-   lxd-agent-loader
+   lxd-agent-loader
  1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
  Need to get 4836 B of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 
lxd-agent-loader all 0.7ubuntu0.1 [4836 B]
- Fetched 4836 B in 0s (268 kB/s)  
+ Fetched 4836 B in 0s (268 kB/s)
  debconf: delaying package configuration, since apt-utils is not installed
  (Reading database ... 14837 files and directories currently installed.)
  Preparing to unpack .../lxd-agent-loader_0.7ubuntu0.1_all.deb ...
  Unpacking lxd-agent-loader (0.7ubuntu0.1) over (0.7) ...
  Setting up lxd-agent-loader (0.7ubuntu0.1) ...
  lxd-agent.service is a disabled or a static unit, not starting it.
  ```
  
  With a fixed lxd-agent-loader package, there should be no abnormal
  closure of the websocket connection during that `apt-get install`
  upgrading the package.
- 
  
  [ Where problems could occur ]
  
  The fix for this upgrade is to not restart the `lxd-agent.service` on
  package upgrade. This means subsequent fixes delivered through package
  updates would not be picked up immediatly. In those case, a VM restarted
  would be required.
  
  This scenario is mitigated by the fact that `lxd-agent.service` already has a 
`Restart=on-failure` directive meaning that if something changes on the LXD 
side causing it to crash, an updated lxd-agent binary would be picked up after 
the first crash.
  Another mitigating factor is that LXD VMs don't require the 
`lxd-agent.service` to be working to trigger an orderly shutdown as ACPI 
signals are sent in the QEMU process.
  
  [ Original description ]
  
  If `do-release-upgrade` is run in LXD VM using `lxc exec 
  bash` or `lxc shell ` to run the upgrade command, the upgrade
  process will restart lxd-agent.service during an upgrade from Jammy to
  Noble, thus causing the `lxc exec` session to be disconnected abruptly.
  
  Simple reproducer steps:
  
  ```
  lxc launch ubuntu:jammy jammy-to-noble --vm
  lxc shell jammy-to-noble
  # now inside the VM
  do-release-upgrade
  
  [snipped]
  Setting up libkeyutils1:amd64 (1.6.3-3build1) ...
  Setting up lxd-agent-loader (0.7) ...
  Error: websocket: close 1006 (abnormal closure): unexpected EOF
  ```
  
  Reported to LXD upstream in
  https://github.com/canonical/lxd/issues/14033

-- 
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:
  lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

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. Here's
the verification procedure on Noble:

$ lxc launch ubuntu-minimal-daily:24.04 v1 --vm
Launching v1
$ lxc shell v1
root@v1:~# sed -i 's/noble-backports$/noble-proposed/' 
/etc/apt/sources.list.d/ubuntu.sources
root@v1:~# apt-get update
...
root@v1:~# apt-get install lxd-agent-loader -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  lxd-agent-loader
1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Need to get 4836 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 
lxd-agent-loader all 0.7ubuntu0.1 [4836 B]
Fetched 4836 B in 0s (268 kB/s)  
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 14837 files and directories currently installed.)
Preparing to unpack .../lxd-agent-loader_0.7ubuntu0.1_all.deb ...
Unpacking lxd-agent-loader (0.7ubuntu0.1) over (0.7) ...
Setting up lxd-agent-loader (0.7ubuntu0.1) ...
lxd-agent.service is a disabled or a static unit, not starting it.
root@v1:~# dpkg -l | grep lxd-agent-loader
ii  lxd-agent-loader   0.7ubuntu0.1  all
  LXD - VM agent loader


That last `dpkg -l | grep lxd-agent-loader` was just to confirm the lxc 
exec/shell session was not interrupted thus confirming the fix.

** 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
  exec` but might be confused by the `do-release-upgrade` command still
  running but being hard to re-attach.
  
  The upload would fix this disconnect problem by simply not stopping the
  `lxd-agent.service` on package upgrade.
  
  [ Test Plan ]
  
  How to reproduce the bug:
  
  ```
- lxc launch ubuntu:jammy jammy-to-noble --vm
- lxc shell jammy-to-noble
- # now inside the VM
- do-release-upgrade
+ $ lxc launch ubuntu-minimal-daily:24.04 v1 --vm
+ $ lxc shell v1
+ # now inside the VM, enable noble-proposed
+ root@v1:~# sed -i 's/noble-backports$/noble-proposed/' 
/etc/apt/sources.list.d/# ubuntu.sources
+ root@v1:~# apt-get update
  
- [snipped]
- Setting up libkeyutils1:amd64 (1.6.3-3build1) ...
- Setting up lxd-agent-loader (0.7) ...
- Error: websocket: close 1006 (abnormal closure): unexpected EOF
+ # install lxd-agent-loader from noble-proposed
+ root@v1:~# apt-get install lxd-agent-loader -t noble-proposed
+ Reading package lists... Done
+ Building dependency tree... Done
+ Reading state information... Done
+ The following packages will be upgraded:
+   lxd-agent-loader
+ 1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
+ Need to get 4836 B of archives.
+ After this operation, 0 B of additional disk space will be used.
+ Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 
lxd-agent-loader all 0.7ubuntu0.1 [4836 B]
+ Fetched 4836 B in 0s (268 kB/s)  
+ debconf: delaying package configuration, since apt-utils is not installed
+ (Reading database ... 14837 files and directories currently installed.)
+ Preparing to unpack .../lxd-agent-loader_0.7ubuntu0.1_all.deb ...
+ Unpacking lxd-agent-loader (0.7ubuntu0.1) over (0.7) ...
+ Setting up lxd-agent-loader (0.7ubuntu0.1) ...
+ lxd-agent.service is a disabled or a static unit, not starting it.
  ```
  
- With a fixed lxd-agent-loader package, there should be no abnormal closure of 
the websocket connection.
- The `do-release-upgrade` should be able to complete without any session 
disconnection.
+ With a fixed lxd-agent-loader package, there should be no abnormal
+ closure of the websocket connection during that `apt-get install`
+ upgrading the package.
+ 
  
  [ Where problems could occur ]
  
  The fix for this upgrade is to not restart the `lxd-agent.service` on
  package upgrade. This means subsequent fixes delivered through package
  updates would not be picked up immediatly. In those case, a VM restarted
  would be required.
  
  This scenario is mitigated by the fact that `lxd-agent.service` already has a 
`Restart=on-failure` directive meaning that if something changes on the LXD 
side causing it to crash, an updated lxd-agent binary would be picked up after 
the first crash.
  Another mitigating factor is that LXD VMs don't require the 
`lxd-agent.service` to be working to trigger an orderly shutdown as ACPI 
signals are sent in the QEMU process.
  
  [ Original description ]
  
  If `do-release-upgrade` is ru

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

** 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:
  lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080277] Re: FFe: lxd-installer should prompt before installing LXD

[Simon Déziel]

** 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". Something:
  
  $ lxc launch ubuntu-minimal:noble c1
  $ lxc shell c1 # accidentally enter `c1`
  # lxc list # try to interact with LXD in the host but mistakenly triggers 
lxd-installer
  
  This last step is taking a while because multiple snaps need to be
  installed due to that `lxc list` being run in the wrong environment
  (instance instead of host). This is why
  https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2073941 and
  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
  were opened/reported.
  
  * Motivation for the FFe:
  
  A better behavior would be for `lxd-installer` to detect if there is a
  terminal and if yes, prompt for a confirmation before doing the lengthy
  installation process. If no terminal is detect, it should assume that
  LXD is to be installed on-demand (current behavior). That is what
  https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+merge/471653
  
  * Additional information:
  
  lxd-installer authoritative sources live at
  https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
  upstream release per se. As such, the only changelog would be:
  
    * scripts/lxc: ask before proceeding if interactive (LP: #2073941, LP:
  #2080277)
  
  This changelog and the associated changes are being proposed for merging
  in https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+merge/471653
  
  The changes themselves are simply to prompt for confirmation before
  proceeding with the lengthy installation if a terminal is detected.
  
  Source build logs:
  
- #FIXME
+ $ dpkg-buildpackage --build=source --no-sign -sa
+ dpkg-buildpackage: info: source package lxd-installer
+ dpkg-buildpackage: info: source version 8
+ dpkg-buildpackage: info: source distribution oracular
+ dpkg-buildpackage: info: source changed by Simon Deziel 

+  dpkg-source --before-build .
+  debian/rules clean
+ dh clean
+dh_auto_clean
+dh_clean
+  dpkg-source -b .
+ dpkg-source: info: using source format '3.0 (native)'
+ dpkg-source: info: building lxd-installer in lxd-installer_8.tar.xz
+ dpkg-source: info: building lxd-installer in lxd-installer_8.dsc
+  dpkg-genbuildinfo --build=source -O../lxd-installer_8_source.buildinfo
+  dpkg-genchanges -sa --build=source -O../lxd-installer_8_source.changes
+ dpkg-genchanges: info: including full source code in upload
+  dpkg-source --after-build .
+ dpkg-buildpackage: info: source-only upload: Debian-native package
  
  Binary build logs:
  
- #FIXME
+ $ dpkg-buildpackage --build=binary --no-sign -sa
+ dpkg-buildpackage: info: source package lxd-installer
+ dpkg-buildpackage: info: source version 8
+ dpkg-buildpackage: info: source distribution oracular
+ dpkg-buildpackage: info: source changed by Simon Deziel 

+ dpkg-buildpackage: info: host architecture amd64
+  dpkg-source --before-build .
+  debian/rules clean
+ dh clean
+dh_auto_clean
+dh_clean
+  debian/rules binary
+ dh binary
+dh_update_autotools_config
+dh_autoreconf
+dh_auto_configure
+dh_auto_build
+   make -j12 "INSTALL=install --strip-program=true"
+ make[1]: Entering directory '/home/ubuntu/lxd-installer'
+ true
+ make[1]: Leaving directory '/home/ubuntu/lxd-installer'
+dh_auto_test
+create-stamp debian/debhelper-build-stamp
+dh_prep
+dh_auto_install --destdir=debian/lxd-installer/
+   make -j12 install 
DESTDIR=/home/ubuntu/lxd-installer/debian/lxd-installer AM_UPDATE_INFO_DIR=no 
"INSTALL=install --strip-program=true"
+ make[1]: Entering directory '/home/ubuntu/lxd-installer'
+ mkdir -p /home/ubuntu/lxd-installer/debian/lxd-installer/usr/sbin 
/home/ubuntu/lxd-installer/debian/lxd-installer/usr/share/lxd-installer
+ install -m 0755 scripts/lxc 
/home/ubuntu/lxd-installer/debian/lxd-installer/usr/sbin
+ ln -sf lxc /home/ubuntu/lxd-installer/debian/lxd-installer/usr/sbin/lxd
+ install -m 0755 lxd-installer-service 
/home/ubuntu/lxd-installer/debian/lxd-installer/usr/share/lxd-installer
+ make[1]: Leaving directory '/home/ubuntu/lxd-installer'
+dh_installdocs
+dh_installchangelogs
+dh_installsystemd
+dh_perl
+dh_link
+dh_strip_nondeterminism
+dh_compress
+dh_fixperms
+dh_missing
+dh_installdeb
+dh_gencontrol
+ dpkg-gencontrol: warning: Depends field of package lxd-installer: 
substitution variable ${shlibs:Depends} used, but is not defined
+dh_md5sums
+dh_builddeb
+ dpkg-deb: building package 'lxd-installer' in '../lxd-installer_8_all.deb'.
+  dpk

[Bug 2080277] [NEW] FFe: lxd-installer should prompt before installing LXD

[Simon Déziel]

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 launch ubuntu-minimal:noble c1
$ lxc shell c1 # accidentally enter `c1`
# lxc list # try to interact with LXD in the host but mistakenly triggers 
lxd-installer

This last step is taking a while because multiple snaps need to be
installed due to that `lxc list` being run in the wrong environment
(instance instead of host). This is why
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2073941 and
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
were opened/reported.

* Motivation for the FFe:

A better behavior would be for `lxd-installer` to detect if there is a
terminal and if yes, prompt for a confirmation before doing the lengthy
installation process. If no terminal is detect, it should assume that
LXD is to be installed on-demand (current behavior). That is what
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
installer/+git/lxd-installer/+merge/471653

* Additional information:

lxd-installer authoritative sources live at
https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
upstream release per se. As such, the only changelog would be:

  * scripts/lxc: ask before proceeding if interactive (LP: #2073941, LP:
#2080277)

This changelog and the associated changes are being proposed for merging
in https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
installer/+git/lxd-installer/+merge/471653

The changes themselves are simply to prompt for confirmation before
proceeding with the lengthy installation if a terminal is detected.

Source build logs:

#FIXME

Binary build logs:

#FIXME

Install logs from a LXD VM:

#FIXME

** Affects: lxd-installer (Ubuntu)
 Importance: Undecided
 Status: New

** 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". Something:
  
  $ lxc launch ubuntu-minimal:noble c1
  $ lxc shell c1 # accidentally enter `c1`
  # lxc list # try to interact with LXD in the host but mistakenly triggers 
lxd-installer
  
  This last step is taking a while because multiple snaps need to be
  installed due to that `lxc list` being run in the wrong environment
  (instance instead of host). This is why
  https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2073941 and
  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
  were opened/reported.
  
- 
  * Motivation for the FFe:
  
  A better behavior would be for `lxd-installer` to detect if there is a
  terminal and if yes, prompt for a confirmation before doing the lengthy
  installation process. If no terminal is detect, it should assume that
  LXD is to be installed on-demand (current behavior). That is what
  https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+merge/471653
  
- 
  * Additional information:
  
  lxd-installer authoritative sources live at
  https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
  upstream release per se. As such, the only changelog would be:
  
-   * scripts/lxc: ask before proceeding if interactive (LP: #2073941, LP:
- #FIXME)
+   * scripts/lxc: ask before proceeding if interactive (LP: #2073941, LP:
+ #2080277)
  
  This changelog and the associated changes are being proposed for merging
  in https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+merge/471653
  
  The changes themselves are simply to prompt for confirmation before
  proceeding with the lengthy installation if a terminal is detected.
  
  Source build logs:
  
  #FIXME
  
- 
  Binary build logs:
  
  #FIXME
  
- 
  Install logs from a LXD VM:
  
  #FIXME

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080277

Title:
  FFe: lxd-installer should prompt before installing LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2080277/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2079406] Re: FFe: update lxd-agent-loader to avoid breaking the `lxc exec` session

[Simon Déziel]

** 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 what caused
  https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936
  for example.
  
  Motivation for the FFe:
  
  This behavior of restarting on package upgrade is problematic especially
  when it happens during do-release-upgrade as it's not obvious how to
  reconnect or pick up where the session was disconnected. As such, the
  end goal of that FFe is to land the fix in Oracular and do a SRU to
  Noble to address the Jammy->Noble upgrade issue it causes.
  
  Additional information:
  
  lxd-agent-loader authoritative sources live at
  https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
- installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
+ installer/+git/lxd-agent-loader/+ref/ubuntu/devel so this is not a new
  upstream release per se. As such, the only changelog would be:
  
    * d/rules: don't stop lxd-agent on upgrade (LP: #2078936, LP:
  #2079406)
  
  This changelog and the associated changes are being proposed for merging
  in https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-
  loader/+git/lxd-agent-loader/+merge/472700
  
  The changes themselves are simply to skip the stopping of the lxd-
  agent.service unit on upgrade as otherwise, stopping that service is
  risking to kill an active `lxc exec` session.
  
  As the d/changelog indicates, this is a bugfix-only update.
  
  Source build logs:
  
  $ dpkg-buildpackage --build=source --no-sign -sa
  dpkg-buildpackage: info: source package lxd-agent-loader
  dpkg-buildpackage: info: source version 0.8
  dpkg-buildpackage: info: source distribution oracular
  dpkg-buildpackage: info: source changed by Simon Deziel 

   dpkg-source --before-build .
   debian/rules clean
  dh clean
     dh_clean
   dpkg-source -b .
  dpkg-source: info: using source format '3.0 (native)'
  dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.tar.xz
  dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.dsc
   dpkg-genbuildinfo --build=source -O../lxd-agent-loader_0.8_source.buildinfo
   dpkg-genchanges -sa --build=source -O../lxd-agent-loader_0.8_source.changes
  dpkg-genchanges: info: including full source code in upload
   dpkg-source --after-build .
  dpkg-buildpackage: info: source-only upload: Debian-native package
  
  Binary build logs:
  
  $ dpkg-buildpackage --build=binary --no-sign -sa
  dpkg-buildpackage: info: source package lxd-agent-loader
  dpkg-buildpackage: info: source version 0.8
  dpkg-buildpackage: info: source distribution oracular
  dpkg-buildpackage: info: source changed by Simon Deziel 

  dpkg-buildpackage: info: host architecture amd64
   dpkg-source --before-build .
   debian/rules clean
  dh clean
     dh_clean
   debian/rules binary
  dh binary
     dh_update_autotools_config
     dh_autoreconf
     create-stamp debian/debhelper-build-stamp
     dh_prep
     dh_auto_install --destdir=debian/lxd-agent-loader/
     dh_install
     dh_installdocs
     dh_installchangelogs
     debian/rules override_dh_installsystemd
  make[1]: Entering directory '/home/ubuntu/lxd-agent-loader'
  # stopping lxd-agent.service kills the `lxc exec` session of a VM
  dh_installsystemd --no-stop-on-upgrade lxd-agent.service
  make[1]: Leaving directory '/home/ubuntu/lxd-agent-loader'
     dh_lintian
     dh_perl
     dh_link
     dh_strip_nondeterminism
     dh_compress
     dh_fixperms
     dh_missing
     dh_installdeb
     dh_gencontrol
     dh_md5sums
     dh_builddeb
  dpkg-deb: building package 'lxd-agent-loader' in 
'../lxd-agent-loader_0.8_all.deb'.
   dpkg-genbuildinfo --build=binary -O../lxd-agent-loader_0.8_amd64.buildinfo
   dpkg-genchanges -sa --build=binary -O../lxd-agent-loader_0.8_amd64.changes
  dpkg-genchanges: info: binary-only upload (no source code included)
   dpkg-source --after-build .
  dpkg-buildpackage: info: binary-only upload (no source included)
  
  Install logs from a LXD VM:
  
  $ lxc launch ubuntu-minimal-daily:24.10 --vm v2
  $ lxc file push lxd-agent-loader_0.8_all.deb v2/tmp/
  $ lxc exec v2 -- bash
  root@v2:~# apt-get install /tmp/lxd-agent-loader_0.8_all.deb
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'lxd-agent-loader' instead of 
'/tmp/lxd-agent-loader_0.8_all.deb'
  The following packages will be upgraded:
    lxd-agent-loader
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/4834 B of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 /tmp/lxd-agent-loader_0.8_all.deb lxd-agent-loader all 0.8 [4834 B]
  debconf: delaying package configuration, since apt-utils is not installed
  (Reading databa

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

** 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
+ exec` but might be confused by the `do-release-upgrade` command still
+ running but being hard to re-attach.
+ 
+ The upload would fix this disconnect problem by simply not stopping the
+ `lxd-agent.service` on package upgrade.
+ 
+ [ Test Plan ]
+ 
+ How to reproduce the bug:
+ 
+ ```
+ lxc launch ubuntu:jammy jammy-to-noble --vm
+ lxc shell jammy-to-noble
+ # now inside the VM
+ do-release-upgrade
+ 
+ [snipped]
+ Setting up libkeyutils1:amd64 (1.6.3-3build1) ...
+ Setting up lxd-agent-loader (0.7) ...
+ Error: websocket: close 1006 (abnormal closure): unexpected EOF
+ ```
+ 
+ With a fixed lxd-agent-loader package, there should be no abnormal closure of 
the websocket connection.
+ The `do-release-upgrade` should be able to complete without any session 
disconnection.
+ 
+ [ Where problems could occur ]
+ 
+ The fix for this upgrade is to not restart the `lxd-agent.service` on
+ package upgrade. This means subsequent fixes delivered through package
+ updates would not be picked up immediatly. In those case, a VM restarted
+ would be required.
+ 
+ This scenario is mitigated by the fact that `lxd-agent.service` already has a 
`Restart=on-failure` directive meaning that if something changes on the LXD 
side causing it to crash, an updated lxd-agent binary would be picked up after 
the first crash.
+ Another mitigating factor is that LXD VMs don't require the 
`lxd-agent.service` to be working to trigger an orderly shutdown as ACPI 
signals are sent in the QEMU process.
+ 
+ [ Original description ]
+ 
  If `do-release-upgrade` is run in LXD VM using `lxc exec 
  bash` or `lxc shell ` to run the upgrade command, the upgrade
  process will restart lxd-agent.service during an upgrade from Jammy to
  Noble, thus causing the `lxc exec` session to be disconnected abruptly.
  
  Simple reproducer steps:
  
  ```
  lxc launch ubuntu:jammy jammy-to-noble --vm
  lxc shell jammy-to-noble
  # now inside the VM
  do-release-upgrade
  
  [snipped]
  Setting up libkeyutils1:amd64 (1.6.3-3build1) ...
  Setting up lxd-agent-loader (0.7) ...
  Error: websocket: close 1006 (abnormal closure): unexpected EOF
  ```
  
  Reported to LXD upstream in
  https://github.com/canonical/lxd/issues/14033

-- 
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:
  lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2079406] Re: FFe: update lxd-agent-loader to avoid breaking the `lxc exec` session

[Simon Déziel]

** 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 what caused
  https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936
  for example.
  
  Motivation for the FFe:
  
  This behavior of restarting on package upgrade is problematic especially
  when it happens during do-release-upgrade as it's not obvious how to
  reconnect or pick up where the session was disconnected. As such, the
  end goal of that FFe is to land the fix in Oracular and do a SRU to
  Noble to address the Jammy->Noble upgrade issue it causes.
  
  Additional information:
  
  lxd-agent-loader authoritative sources live at
  https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
  installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
  upstream release per se. As such, the only changelog would be:
  
    * d/rules: don't stop lxd-agent on upgrade (LP: #2078936, LP:
  #2079406)
  
- This changelog and associated changes are being proposed for merging in
- https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-
+ This changelog and the associated changes are being proposed for merging
+ in https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-
  loader/+git/lxd-agent-loader/+merge/472700
+ 
+ The changes themselves are simply to skip the stopping of the lxd-
+ agent.service unit on upgrade as otherwise, stopping that service is
+ risking to kill an active `lxc exec` session.
  
  As the d/changelog indicates, this is a bugfix-only update.
  
  Source build logs:
  
  $ dpkg-buildpackage --build=source --no-sign -sa
  dpkg-buildpackage: info: source package lxd-agent-loader
  dpkg-buildpackage: info: source version 0.8
  dpkg-buildpackage: info: source distribution oracular
  dpkg-buildpackage: info: source changed by Simon Deziel 

   dpkg-source --before-build .
   debian/rules clean
  dh clean
     dh_clean
   dpkg-source -b .
  dpkg-source: info: using source format '3.0 (native)'
  dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.tar.xz
  dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.dsc
   dpkg-genbuildinfo --build=source -O../lxd-agent-loader_0.8_source.buildinfo
   dpkg-genchanges -sa --build=source -O../lxd-agent-loader_0.8_source.changes
  dpkg-genchanges: info: including full source code in upload
   dpkg-source --after-build .
  dpkg-buildpackage: info: source-only upload: Debian-native package
  
  Binary build logs:
  
  $ dpkg-buildpackage --build=binary --no-sign -sa
  dpkg-buildpackage: info: source package lxd-agent-loader
  dpkg-buildpackage: info: source version 0.8
  dpkg-buildpackage: info: source distribution oracular
  dpkg-buildpackage: info: source changed by Simon Deziel 

  dpkg-buildpackage: info: host architecture amd64
   dpkg-source --before-build .
   debian/rules clean
  dh clean
     dh_clean
   debian/rules binary
  dh binary
     dh_update_autotools_config
     dh_autoreconf
     create-stamp debian/debhelper-build-stamp
     dh_prep
     dh_auto_install --destdir=debian/lxd-agent-loader/
     dh_install
     dh_installdocs
     dh_installchangelogs
     debian/rules override_dh_installsystemd
  make[1]: Entering directory '/home/ubuntu/lxd-agent-loader'
  # stopping lxd-agent.service kills the `lxc exec` session of a VM
  dh_installsystemd --no-stop-on-upgrade lxd-agent.service
  make[1]: Leaving directory '/home/ubuntu/lxd-agent-loader'
     dh_lintian
     dh_perl
     dh_link
     dh_strip_nondeterminism
     dh_compress
     dh_fixperms
     dh_missing
     dh_installdeb
     dh_gencontrol
     dh_md5sums
     dh_builddeb
  dpkg-deb: building package 'lxd-agent-loader' in 
'../lxd-agent-loader_0.8_all.deb'.
   dpkg-genbuildinfo --build=binary -O../lxd-agent-loader_0.8_amd64.buildinfo
   dpkg-genchanges -sa --build=binary -O../lxd-agent-loader_0.8_amd64.changes
  dpkg-genchanges: info: binary-only upload (no source code included)
   dpkg-source --after-build .
  dpkg-buildpackage: info: binary-only upload (no source included)
  
  Install logs from a LXD VM:
  
  $ lxc launch ubuntu-minimal-daily:24.10 --vm v2
  $ lxc file push lxd-agent-loader_0.8_all.deb v2/tmp/
  $ lxc exec v2 -- bash
  root@v2:~# apt-get install /tmp/lxd-agent-loader_0.8_all.deb
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'lxd-agent-loader' instead of 
'/tmp/lxd-agent-loader_0.8_all.deb'
  The following packages will be upgraded:
    lxd-agent-loader
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/4834 B of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 /tmp/lxd-agent-loader_0.8_all.deb lxd-agent-loader all 0.8 [4834 B]
  debconf: delaying package 

[Bug 2079406] [NEW] FFe: update lxd-agent-loader to avoid breaking the `lxc exec` session

[Simon Déziel]

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://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936
for example.

Motivation for the FFe:

This behavior of restarting on package upgrade is problematic especially
when it happens during do-release-upgrade as it's not obvious how to
reconnect or pick up where the session was disconnected. As such, the
end goal of that FFe is to land the fix in Oracular and do a SRU to
Noble to address the Jammy->Noble upgrade issue it causes.

Additional information:

lxd-agent-loader authoritative sources live at
https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/lxd-
installer/+git/lxd-installer/+ref/ubuntu/devel so this is not a new
upstream release per se. As such, the only changelog would be:

  * d/rules: don't stop lxd-agent on upgrade (LP: #2078936, LP:
#2079406)

This changelog and associated changes are being proposed for merging in
https://code.launchpad.net/~sdeziel/ubuntu/+source/lxd-agent-
loader/+git/lxd-agent-loader/+merge/472700

As the d/changelog indicates, this is a bugfix-only update.

Source build logs:

$ dpkg-buildpackage --build=source --no-sign -sa
dpkg-buildpackage: info: source package lxd-agent-loader
dpkg-buildpackage: info: source version 0.8
dpkg-buildpackage: info: source distribution oracular
dpkg-buildpackage: info: source changed by Simon Deziel 

 dpkg-source --before-build .
 debian/rules clean
dh clean
   dh_clean
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.tar.xz
dpkg-source: info: building lxd-agent-loader in lxd-agent-loader_0.8.dsc
 dpkg-genbuildinfo --build=source -O../lxd-agent-loader_0.8_source.buildinfo
 dpkg-genchanges -sa --build=source -O../lxd-agent-loader_0.8_source.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build .
dpkg-buildpackage: info: source-only upload: Debian-native package

Binary build logs:

$ dpkg-buildpackage --build=binary --no-sign -sa
dpkg-buildpackage: info: source package lxd-agent-loader
dpkg-buildpackage: info: source version 0.8
dpkg-buildpackage: info: source distribution oracular
dpkg-buildpackage: info: source changed by Simon Deziel 

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   create-stamp debian/debhelper-build-stamp
   dh_prep
   dh_auto_install --destdir=debian/lxd-agent-loader/
   dh_install
   dh_installdocs
   dh_installchangelogs
   debian/rules override_dh_installsystemd
make[1]: Entering directory '/home/ubuntu/lxd-agent-loader'
# stopping lxd-agent.service kills the `lxc exec` session of a VM
dh_installsystemd --no-stop-on-upgrade lxd-agent.service
make[1]: Leaving directory '/home/ubuntu/lxd-agent-loader'
   dh_lintian
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_installdeb
   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'lxd-agent-loader' in 
'../lxd-agent-loader_0.8_all.deb'.
 dpkg-genbuildinfo --build=binary -O../lxd-agent-loader_0.8_amd64.buildinfo
 dpkg-genchanges -sa --build=binary -O../lxd-agent-loader_0.8_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)

Install logs from a LXD VM:

$ lxc launch ubuntu-minimal-daily:24.10 --vm v2
$ lxc file push lxd-agent-loader_0.8_all.deb v2/tmp/
$ lxc exec v2 -- bash
root@v2:~# apt-get install /tmp/lxd-agent-loader_0.8_all.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'lxd-agent-loader' instead of 
'/tmp/lxd-agent-loader_0.8_all.deb'
The following packages will be upgraded:
  lxd-agent-loader
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4834 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /tmp/lxd-agent-loader_0.8_all.deb lxd-agent-loader all 0.8 [4834 B]
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 14834 files and directories currently installed.)
Preparing to unpack .../lxd-agent-loader_0.8_all.deb ...
Unpacking lxd-agent-loader (0.8) over (0.7) ...
Setting up lxd-agent-loader (0.8) ...
lxd-agent.service is a disabled or a static unit, not starting it.
root@v2:~#

In the above, we see the `lxc exec` session was not disconnected thus
confirming the bug fix.

** Affects: lxd-agent-loader (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Problem descripti

[Bug 2078936] Re: lxd-agent restarts during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

** 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.
https://bugs.launchpad.net/bugs/2078936

Title:
  lxd-agent restarts during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2078936] [NEW] lxd-agent restart during do-release-upgrade breaking the `lxc exec` connection

[Simon Déziel]

Public bug reported:

If `do-release-upgrade` is run in LXD VM using `lxc exec 
bash` or `lxc shell ` to run the upgrade command, the upgrade
process will restart lxd-agent.service during an upgrade from Jammy to
Noble, thus causing the `lxc exec` session to be disconnected abruptly.

Simple reproducer steps:

```
lxc launch ubuntu:jammy jammy-to-noble --vm
lxc shell jammy-to-noble
# now inside the VM
do-release-upgrade

[snipped]
Setting up libkeyutils1:amd64 (1.6.3-3build1) ...
Setting up lxd-agent-loader (0.7) ...
Error: websocket: close 1006 (abnormal closure): unexpected EOF
```

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)

-- 
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:
  lxd-agent restart during do-release-upgrade breaking the `lxc exec`
  connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2078936/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064176] Re: LXD fan bridge causes blocked tasks

[Simon Déziel]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064176

Title:
  LXD fan bridge causes blocked tasks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2073941] Re: lxd-installer should prompt before installing LXD

[Simon Déziel]

** 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 trigger the on-
  demand installation of LXD's snap which takes a while.
  
  A better behavior would be for `lxd-installer` to detect if there is a
  terminal and if yes, prompt for a confirmation before doing the lengthy
  installation process. If no terminal is detect, it should assume that
  LXD is to be installed on-demand (current behavior).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073941

Title:
  lxd-installer should prompt before installing LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2073941/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2077262] Re: package nginx 1.24.0-2ubuntu7 failed to install/upgrade: installed nginx package post-installation script subprocess returned error exit status 1

[Simon Déziel]

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 easily get larger 
parameters from Mozilla as hinted in 
https://ssl-config.mozilla.org/#server=nginx&version=1.24.0&config=intermediate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077262

Title:
  package nginx 1.24.0-2ubuntu7 failed to install/upgrade: installed
  nginx package post-installation script subprocess returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2077262/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1980848] Re: arc_summary doesn't work with HWE kernel 5.15

[Simon Déziel]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1980848/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1980848] Re: arc_summary doesn't work with HWE kernel 5.15

[Simon Déziel]

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, in get_kstats
with open(PROC_PATH+section, 'r') as proc_location:
FileNotFoundError: [Errno 2] No such file or directory: 
'/proc/spl/kstat/zfs/xuio_stats'

After enabling focal-proposed, installed 0.8.3-1ubuntu12.18:

# apt-get install zfsutils-linux
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
   libnvpair1linux (0.8.3-1ubuntu12.18)
   libuutil1linux (0.8.3-1ubuntu12.18)
   libzfs2linux (0.8.3-1ubuntu12.18)
   libzpool2linux (0.8.3-1ubuntu12.18)
Suggested packages:
   nfs-kernel-server (1:1.3.4-2.5ubuntu3.7)
   samba-common-bin (2:4.15.13+dfsg-0ubuntu0.20.04.8)
   zfs-initramfs (0.8.3-1ubuntu12.18)
   | zfs-dracut (0.8.3-1ubuntu12.17)
Recommended packages:
   zfs-zed (0.8.3-1ubuntu12.18)
The following packages will be upgraded:
   libnvpair1linux (0.8.3-1ubuntu12.17 => 0.8.3-1ubuntu12.18)
   libuutil1linux (0.8.3-1ubuntu12.17 => 0.8.3-1ubuntu12.18)
   libzfs2linux (0.8.3-1ubuntu12.17 => 0.8.3-1ubuntu12.18)
   libzpool2linux (0.8.3-1ubuntu12.17 => 0.8.3-1ubuntu12.18)
   zfsutils-linux (0.8.3-1ubuntu12.17 => 0.8.3-1ubuntu12.18)
5 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 1,463 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
zfsutils-linux amd64 0.8.3-1ubuntu12.18 [354 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libuutil1linux amd64 0.8.3-1ubuntu12.18 [41.8 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libzfs2linux amd64 0.8.3-1ubuntu12.18 [207 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libzpool2linux amd64 0.8.3-1ubuntu12.18 [812 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
libnvpair1linux amd64 0.8.3-1ubuntu12.18 [48.4 kB]


And it now works:

$ arc_summary


ZFS Subsystem ReportMon Aug 05 08:58:13 2024
Linux 5.15.0-117-generic  2.1.5-1ubuntu6~22.04.4
Machine: mars (x86_64)2.1.5-1ubuntu6~22.04.4

ARC status:  HEALTHY
Memory throttle count: 0

ARC size (current):82.7 %1.5 GiB
Target size (adaptive):85.6 %1.6 GiB
Min size (hard limit):  6.2 %  119.3 MiB
Max size (high water):   16:11.9 GiB
Most Frequently Used (MFU) cache size: 92.1 %1.3 GiB
Most Recently Used (MRU) cache size:7.9 %  116.4 MiB
Metadata cache size (hard limit):  75.0 %1.4 GiB
Metadata cache size (current): 94.9 %1.3 GiB
Dnode cache size (hard limit): 10.0 %  143.2 MiB
Dnode cache size (current): 8.9 %   12.8 MiB

ARC hash breakdown:
Elements max: 249.5k
Elements current:  99.7 % 248.6k
Collisions:   178.0k
Chain max: 6
Chains:43.0k

ARC misc:
Deleted:  12
Mutex misses:  0
Eviction skips:1

ARC total accesses (hits + misses): 9.4M
Cache hit ratio:   97.4 %   9.2M
Cache miss ratio:   2.6 % 249.3k
Actual hit ratio (MFU + MRU hits): 97.3 %   9.2M
Data demand efficiency:98.7 % 418.0k
Data prefetch efficiency:   5.5 %993

Cache hits by cache type:
Most frequently used (MFU):93.0 %   8.5M
Most recently used (MRU):   7.0 % 640.4k
Most frequently used (MFU) ghost:   0.0 %  0
Most recently used (MRU) ghost: 0.0 %  0
Anonymously used: < 0.1 %   1.6k

Cache hits by data type:
Demand data:4.5 % 412.4k
Dem

[Bug 2073941] [NEW] lxd-installer should prompt before installing LXD

[Simon Déziel]

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 behavior would be for `lxd-installer` to detect if there is a
terminal and if yes, prompt for a confirmation before doing the lengthy
installation process. If no terminal is detect, it should assume that
LXD is to be installed on-demand (current behavior).

** Affects: lxd-installer (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/2073941

Title:
  lxd-installer should prompt before installing LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2073941/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1995194] Re: lxd init fails with 'Address already in use'

[Simon Déziel]

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 improve on. LXD really needs that dnsmasq listener
so bind9 taking it over is nothing LXD can do about.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1995194

Title:
  lxd init fails with 'Address already in use'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1995194/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1995194] Re: lxd init fails with 'Address already in use'

[Simon Déziel]

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 has a feature that spawns listeners on newly created
interfaces, so maybe MAAS could turn that feature off to play more
nicely with other listeners?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1995194

Title:
  lxd init fails with 'Address already in use'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1995194/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065537] Re: python3-pylxd broken and taken from wrong source

[Simon Déziel]

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.
https://bugs.launchpad.net/bugs/2065537

Title:
  python3-pylxd broken and taken from wrong source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/2065537/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072702] Re: AppArmor profile prevents use of TLS keys and certificates

[Simon Déziel]

@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 bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072702

Title:
  AppArmor profile prevents use of TLS keys and certificates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2072702/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072656] [NEW] Missing dependency on libsnappy1v5

[Simon Déziel]

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-gnu/ceph/compressor/libceph_snappy.so.2.0.0
/usr/lib/x86_64-linux-gnu/ceph/compressor/libceph_snappy.so
/usr/lib/x86_64-linux-gnu/ceph/compressor/libceph_snappy.so.2
```

This `libceph_snappy.so.2.0.0` in turn depends on `libsnappy.so.1` but
it's not found:

```
root@c1:~# ldd /usr/lib/x86_64-linux-gnu/ceph/compressor/libceph_snappy.so.2.0.0
linux-vdso.so.1 (0x7ffd72b74000)
libsnappy.so.1 => not found
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7643adce4000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7643adcb7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7643adaa5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7643ad9bc000)
/lib64/ld-linux-x86-64.so.2 (0x7643adf72000)
```

This `libsnappy.so.1` is normally provided by the `libsnappy1v5` package
and installing it manually fixes it:

```
root@c1:~# apt-get install -y libsnappy1v5
...
root@c1:~# ldd /usr/lib/x86_64-linux-gnu/ceph/compressor/libceph_snappy.so.2.0.0
linux-vdso.so.1 (0x7ffdb7b25000)
libsnappy.so.1 => /lib/x86_64-linux-gnu/libsnappy.so.1 
(0x7537db3ed000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7537db17)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7537db143000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7537daf31000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7537dae48000)
/lib64/ld-linux-x86-64.so.2 (0x7537db409000)
```

For some reason, `ceph-common` had a dependency on `libsnappy1v5` in
Jammy but it was lost afterward, causing this issue.

** Affects: ceph (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/2072656

Title:
  Missing dependency on libsnappy1v5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2072656/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069921] Re: gzip_static directive stopped working

[Simon Déziel]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069921

Title:
  gzip_static directive stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2069921/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble

[Simon Déziel]

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-image-6.8.0-1007-raspi (6.8.0-1007.7)
   linux-modules-6.8.0-1007-raspi (6.8.0-1007.7)
The following packages will be upgraded:
   apparmor (4.0.0-beta3-0ubuntu3 => 4.0.1-0ubuntu0.24.04.2)
   apt (2.7.14build2 => 2.8.0)
   apt-utils (2.7.14build2 => 2.8.0)
   dracut-install (060+5-1ubuntu3 => 060+5-1ubuntu3.1)
   libapparmor1 (4.0.0-beta3-0ubuntu3 => 4.0.1-0ubuntu0.24.04.2)
   libapt-pkg6.0t64 (2.7.14build2 => 2.8.0)
   libgnutls30t64 (3.8.3-1.1ubuntu3 => 3.8.3-1.1ubuntu3.1)
   libpam-modules (1.5.3-5ubuntu5 => 1.5.3-5ubuntu5.1)
   libpam-modules-bin (1.5.3-5ubuntu5 => 1.5.3-5ubuntu5.1)
   libpam-runtime (1.5.3-5ubuntu5 => 1.5.3-5ubuntu5.1)
   libpam0g (1.5.3-5ubuntu5 => 1.5.3-5ubuntu5.1)
   linux-image-raspi (6.8.0-1005.5 => 6.8.0-1007.7)
   login (1:4.13+dfsg1-4ubuntu3 => 1:4.13+dfsg1-4ubuntu3.2)
   lxd-installer (4 => 4ubuntu0.1)
   passwd (1:4.13+dfsg1-4ubuntu3 => 1:4.13+dfsg1-4ubuntu3.2)
   python3-distupgrade (1:24.04.18 => 1:24.04.19)
   python3-software-properties (0.99.48 => 0.99.49)
   software-properties-common (0.99.48 => 0.99.49)
   ubuntu-pro-client (32.3~24.04 => 32.3.1~24.04)
   ubuntu-pro-client-l10n (32.3~24.04 => 32.3.1~24.04)
   ubuntu-release-upgrader-core (1:24.04.18 => 1:24.04.19)
21 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
...

root@ubuntu:~# uname -a
Linux ubuntu 6.8.0-1007-raspi #7-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 24 10:21:12 
UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

root@ubuntu:~# lxc launch ubuntu-daily:n/armhf nobletest
root@ubuntu:~# lxc exec nobletest -- hostname
nobletest
root@ubuntu:~# lxc ls
+---+-+-+--+---+---+
|   NAME|  STATE  |IPV4 | IPV6  
   |   TYPE| SNAPSHOTS |
+---+-+-+--+---+---+
| nobletest | RUNNING | 10.123.62.15 (eth0) | 
fd42:32a5:f6b4:f6f:216:3eff:fe93:f224 (eth0) | CONTAINER | 0 |
+---+-+-+--+---+---+
```


** Tags removed: verification-needed-noble-linux-raspi
** Tags added: verification-done-noble-linux-raspi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176

Title:
  Cannot launch armhf containers on arm64 host under noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069921] Re: gzip_static directive stopped working

[Simon Déziel]

@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 | grep ETag
  ETag: "667af11b-124fd"


Also, re `touch *`, I'm not entirely sure on how you are doing the "ahead of 
time compression" but I get good result from `gzip --best --keep --force 
--no-name` which cause the `.gz` files to be created with a newer timestamp 
naturally.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069921

Title:
  gzip_static directive stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2069921/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069921] Re: gzip_static directive stopped working

[Simon Déziel]

@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 | grep 
ETag
  ETag: "66720e58-15601"
$ wget -qSO /dev/null 
https://villadeus.com/wp-includes/js/jquery/jquery.min.js.gz?ver=3.7.1 2>&1 | 
grep ETag
  ETag: "66720f0c-7656"
$ wget --compress gzip -qSO /dev/null 
https://villadeus.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 2>&1 | grep 
ETag
  ETag: "66720f0c-7656"

On one of my working system with `gzip_static` working, the ETag is
always identical which makes sense if I understand the feature properly.

Are you 100% sure your `gzip`'ed files are based on the uncompressed
ones? `ls --full-time` might be handy to confirm.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069921

Title:
  gzip_static directive stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2069921/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069754] [NEW] lxd-installer wait message confuses version checkers

[Simon Déziel]

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 -- apt-get install --no-install-recommends -y git
$ lxc exec o1 -- git clone https://github.com/canonical/lxd-pkg-snap.git

$ lxc exec o1 -- snap wait system seed
$ lxc exec o1 -- snap install --classic snapcraft

$ lxc exec o1 -- sh -c 'cd /root/lxd-pkg-snap && snapcraft'
craft-providers error: Failed to parse LXD version.
Version data returned: 'Installing' 
 
Full execution log: 
'/root/.local/state/snapcraft/log/snapcraft-20240618-151045.662527.log'


In the above, we see that `snapcraft` tried to interpret the first word on 
stdout ("Installing") as the LXD version but that's failing for obvious reasons.

lxd-installer should not output anything to stdout as that should be
left to the real `lxd` and `lxc` commands.

** Affects: lxd-installer (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/2069754

Title:
  lxd-installer wait message confuses version checkers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2069754/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069466] Re: nginx install no longer works unless ipv6 is enabled

[Simon Déziel]

*** 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 example.

If you don't want to use/configure/firewall your IPv6 setup, there are
other ways to disable it that are less disruptive. One way is to add
`link-local: []` and `accept-ra: no` to your NIC config in your netplan.

Regarding the TLS configuration, this is the subject of
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1883951

** This bug has been marked a duplicate of bug 1743592
   NGINX fails to start/install/upgrade if IPv6 is completely disabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069466

Title:
  nginx install no longer works unless ipv6 is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/2069466/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1597017] Re: mount rules grant excessive permissions

[Simon Déziel]

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-2ubuntu2.4)
End-Date: 2024-04-18  12:48:25

I'll leave it to someone else to decide if that's enough to mark it as
`verification-done-jammy`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597017

Title:
  mount rules grant excessive permissions

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1597017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067800] Re: needrestart should avoid restarting runner-provisioner.service

[Simon Déziel]

** 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.net/ubuntu/+source/needrestart/+bug/2067800/comments/2)
+ users of self-hosted runners might have images lacking the workaround.
+ 
+ The fix is to add `runner-provisioner.service` to the override/exclusion list 
to prevent automatic restart of that service.
+  
+ [ Test Plan ]
+ 
+ Since GitHub patched the main configuration file to do the exclusion, this 
needs to be undone before doing the verification.
+ The verification itself should ideally be done on a GitHub runner
+ 
+ 1) Undo GitHub config workaround:
+ sudo sed -i '/^\s*qr(^runner-provisioner)\s*=>\s*0,$/d' 
/etc/needrestart/needrestart.conf
+ 
+ 2) Install fixed package from proposed
+ echo "deb http://archive.ubuntu.com/ubuntu noble-proposed main" | sudo tee 
/etc/apt/sources.list
+ sudo apt update
+ sudo apt install -y -t noble-proposed needrestart
+ 
+ 3) Reinstall something that would cause the runner-provisioner.service unit 
to be restarted:
+ sudo apt reinstall libc6
+ sleep 5
+ echo Success
+ 
+ 
+ Those instructions are available in this workflow:
+ 
+ https://github.com/simondeziel/needrestart-
+ ghaction/blob/main/.github/workflows/blank.yml
+ 
+ [ Where problems could occur ]
+ 
+ It is possible that other environment (non GitHub runners) have a systemd 
unit by the same name and excluding the service from the restart-able list 
would prevent their service from being restarted automatically.
+
+ The packages in the Ubuntu archive don't contain any systemd unit by that 
name so this risk is only for "external" packages.
+ 
+ [ Original bug description ]
+ 
  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.service 
runner-provisioner.service systemd-journald.service systemd-networkd.service 
systemd-resolved.service systemd-udevd.service udisks2.service 
walinuxagent.service
  Terminated
  ```
  
  While the above shows multiple services being restarted, "artificially"
  restarting just runner-provisioner.service has shown to cause an
  immediate failure (as seen in https://github.com/canonical/lxd-
  ci/actions/runs/9323021640/job/25665299316?pr=178)
  
  ```
  + sudo systemctl restart runner-provisioner.service
  Error: Process completed with exit code 143.
  ```
  
  If needrestart has a way to exclude services from being restarted,
  runner-provisioner.service should be added to the list.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067800] Re: needrestart should avoid restarting runner-provisioner.service

[Simon Déziel]

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 default selection (hash of regex).
$nrconf{override_cont} = {
qr(^runner-provisioner) => 0,
};
```

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067800] Re: needrestart should avoid restarting runner-provisioner.service

[Simon Déziel]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel

[Simon Déziel]

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: verification-done-noble-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064508

Title:
  re-enable Ubuntu FAN in the Noble kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069198] Re: OpenZFS High Load Average

[Simon Déziel]

*** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069198

Title:
  OpenZFS High Load Average

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2069198/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`

[Simon Déziel]

@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 to begin transaction: context
  deadline exceeded`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2039148] Re: lxd-installer can race or temp-fail and then block itself

[Simon Déziel]

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 => Confirmed

** Changed in: lxd-installer (Ubuntu Mantic)
   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/2039148

Title:
  lxd-installer can race or temp-fail and then block itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2039148/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2039148] Re: lxd-installer can race or temp-fail and then block itself

[Simon Déziel]

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: [Errno 104] Connection reset by peer
```

It seems to be due to snapd not being fully seeded when the `snap
install lxd` request comes in:

```
$ lxc delete -f c1; lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3.5; lxc 
exec c1 -- systemctl status snapd.seeded.service; lxc exec c1 -- lxc list; lxc 
exec c1 -- sh -c 'systemctl status lxd-installer@*.service'
Creating c1
Starting c1
● snapd.seeded.service - Wait until snapd is fully seeded
 Loaded: loaded (/usr/lib/systemd/system/snapd.seeded.service; enabled; 
preset: enabled)
 Active: activating (start) since Tue 2024-06-04 20:49:32 UTC; 636ms ago
   Main PID: 333 (snap)
  Tasks: 6 (limit: 36997)
 Memory: 13.2M (peak: 13.7M)
CPU: 550ms
 CGroup: /system.slice/snapd.seeded.service
 └─333 /usr/bin/snap wait system seed.loaded

Jun 04 20:49:32 c1 systemd[1]: Starting snapd.seeded.service - Wait until snapd 
is fully seeded...
Installing LXD snap, please be patient.
Traceback (most recent call last):
  File "", line 1, in 
ConnectionResetError: [Errno 104] Connection reset by peer
/usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
Error: Command not found
× lxd-installer@0-411-0.service - Helper to install lxd snap on demand (PID 
411/UID 0)
 Loaded: loaded (/usr/lib/systemd/system/lxd-installer@.service; static)
 Active: failed (Result: exit-code) since Tue 2024-06-04 20:49:33 UTC; 1min 
30s ago
   Duration: 240ms
TriggeredBy: ● lxd-installer.socket
Process: 414 ExecStart=/bin/sh -eux 
/usr/share/lxd-installer/lxd-installer-service (code=exited, status=10)
   Main PID: 414 (code=exited, status=10)
CPU: 24ms

Jun 04 20:49:33 c1 sh[416]: + 
PRIVACY_POLICY_URL=https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
Jun 04 20:49:33 c1 sh[416]: + UBUNTU_CODENAME=noble
Jun 04 20:49:33 c1 sh[416]: + LOGO=ubuntu-logo
Jun 04 20:49:33 c1 sh[416]: + track=5.21
Jun 04 20:49:33 c1 sh[416]: + [ -n 24.04 ]
Jun 04 20:49:33 c1 sh[416]: + echo 5.21/stable/ubuntu-24.04
Jun 04 20:49:33 c1 sh[414]: + snap install lxd 
--channel=5.21/stable/ubuntu-24.04
Jun 04 20:49:33 c1 sh[417]: error: too early for operation, device not yet 
seeded or device model not acknowledged
Jun 04 20:49:33 c1 systemd[1]: lxd-installer@0-411-0.service: Main process 
exited, code=exited, status=10/n/a
Jun 04 20:49:33 c1 systemd[1]: lxd-installer@0-411-0.service: Failed with 
result 'exit-code'.
```

This same error can be reproduced more simply with:

```
$ lxc launch ubuntu-minimal-daily:24.04 c1; sleep 3; lxc exec c1 -- snap 
install lxd
Creating c1
Starting c1
error: too early for operation, device not yet seeded or device model not 
acknowledged
```

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039148

Title:
  lxd-installer can race or temp-fail and then block itself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2039148/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067800] [NEW] needrestart should avoid restarting runner-provisioner.service

[Simon Déziel]

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.service 
runner-provisioner.service systemd-journald.service systemd-networkd.service 
systemd-resolved.service systemd-udevd.service udisks2.service 
walinuxagent.service
Terminated
```

While the above shows multiple services being restarted, "artificially"
restarting just runner-provisioner.service has shown to cause an
immediate failure (as seen in https://github.com/canonical/lxd-
ci/actions/runs/9323021640/job/25665299316?pr=178)

```
+ sudo systemctl restart runner-provisioner.service
Error: Process completed with exit code 143.
```

If needrestart has a way to exclude services from being restarted,
runner-provisioner.service should be added to the list.

** Affects: needrestart (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/2067800

Title:
  needrestart should avoid restarting runner-provisioner.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2067800/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives)

[Simon Déziel]

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_TIME off on arm64 (64k & derivatives)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038582/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063298] Re: deprecate ubuntu-fan in Noble

[Simon Déziel]

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 Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2063298/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067425] [NEW] lxd-installer should default to pulling LXD from the $LTS/stable/ubuntu-XX.YY channel

[Simon Déziel]

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/branch.

** Affects: lxd-installer (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/2067425

Title:
  lxd-installer should default to pulling LXD from the
  $LTS/stable/ubuntu-XX.YY channel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2067425/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble

[Simon Déziel]

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://github.com/canonical/lxd/issues/13512
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176

Title:
  Cannot launch armhf containers on arm64 host under noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

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 other bug(s) to be fix released
before removing the block-proposed-noble tag from here, right?

-- 
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 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic

[Simon Déziel]

** 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 images since Noble+ so
- the unminimize logic in https://git.launchpad.net/livecd-
- rootfs/tree/live-build/auto/build?h=ubuntu/noble#n290 and
+ The LXD snap is no longer seeded in any images since Noble+ so the
+ unminimize logic in https://git.launchpad.net/livecd-rootfs/tree/live-
+ build/auto/build?h=ubuntu/noble#n290 and
  https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  server/hooks/01-unminimize.chroot_early?h=ubuntu/noble#n17 is no longer
  required.
  
  lxd-installer can remain installed.
  
  This applies for Noble+ so requires SRU back 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/2066905

Title:
  LXD snap no longer seeded in any images so does not need special
  handling in unminimize logic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

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* /usr/sbin/lxd*
lrwxrwxrwx 1 root root   9 May 22 14:27 /sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /sbin/lxd.REAL*
lrwxrwxrwx 1 root root   9 May 22 14:27 /usr/sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /usr/sbin/lxd.REAL*
root@c1:~# sed -i 's/noble-backports/noble-proposed/' 
/etc/apt/sources.list.d/ubuntu.sources
root@c1:~# apt-get update -qq
root@c1:~# apt-get install lxd-installer -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  lxd-installer
1 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
Need to get 3926 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 lxd-installer 
all 4ubuntu0.1 [3926 B]
Fetched 3926 B in 0s (107 kB/s) 
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 12554 files and directories currently installed.)
Preparing to unpack .../lxd-installer_4ubuntu0.1_all.deb ...
Unpacking lxd-installer (4ubuntu0.1) over (4) ...
Setting up lxd-installer (4ubuntu0.1) ...
root@c1:~# ll /sbin/lxd* /usr/sbin/lxd*
lrwxrwxrwx 1 root root   9 May 22 14:27 /sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 589 May  7 23:33 /sbin/lxd.REAL*
lrwxrwxrwx 1 root root   9 May 22 14:27 /usr/sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 589 May  7 23:33 /usr/sbin/lxd.REAL*
root@c1:~# lxd --version
true (GNU coreutils) 9.4
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Jim Meyering.
```

So it seems this issue was not visible before because `lxd-installer`
was not upgraded.

-- 
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 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

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 and the diversion is presumably
not respected due to confusion between `/usr/sbin/lxd` and `/sbin/lxd`.
Here's the reproducer:

```
$ lxc launch ubuntu-minimal-daily:24.04 c1
$ lxc shell c1
root@c1:~# dpkg-divert --add --divert /usr/sbin/lxd.REAL --rename /usr/sbin/lxd
Adding 'local diversion of /usr/sbin/lxd to /usr/sbin/lxd.REAL'
root@c1:~# ln -s /bin/true /usr/sbin/lxd
root@c1:~# ll /sbin/lxd* /usr/sbin/lxd*
lrwxrwxrwx 1 root root   9 May 22 14:20 /sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /sbin/lxd.REAL*
lrwxrwxrwx 1 root root   9 May 22 14:20 /usr/sbin/lxd -> /bin/true*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /usr/sbin/lxd.REAL*
root@c1:~# sed -i 's/noble-backports/noble-proposed/' 
/etc/apt/sources.list.d/ubuntu.sources
root@c1:~# apt-get -qq update
root@c1:~# apt-get install lxd-installer -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  lxd-installer
1 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
Need to get 3926 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 lxd-installer 
all 4ubuntu0.1 [3926 B]
Fetched 3926 B in 0s (106 kB/s) 
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 12555 files and directories currently installed.)
Preparing to unpack .../lxd-installer_4ubuntu0.1_all.deb ...
Unpacking lxd-installer (4ubuntu0.1) over (4) ...
Setting up lxd-installer (4ubuntu0.1) ...
root@c1:~# ll /sbin/lxd* /usr/sbin/lxd*
-rwxr-xr-x 1 root root 589 May  7 23:33 /sbin/lxd*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /sbin/lxd.REAL*
-rwxr-xr-x 1 root root 589 May  7 23:33 /usr/sbin/lxd*
-rwxr-xr-x 1 root root 372 Jan 11 16:58 /usr/sbin/lxd.REAL*
```

-- 
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 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error

[Simon Déziel]

@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

Title:
  lxd vga console throws "Operation not permitted" error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error

[Simon Déziel]

@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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057927

Title:
  lxd vga console throws "Operation not permitted" error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors

[Simon Déziel]

@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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763

Title:
  qemu-system-amd64 max cpus is too low for latest processors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

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-installer_4ubuntu0.1_all.deb u1/tmp/

$ lxc exec u1 -- apt-get install /tmp/lxd-installer_4ubuntu0.1_all.deb  

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'lxd-installer' instead of 
'/tmp/lxd-installer_4ubuntu0.1_all.deb'
The following packages will be upgraded:
  lxd-installer
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3926 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /tmp/lxd-installer_4ubuntu0.1_all.deb lxd-installer all 4ubuntu0.1 [3926 
B]
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 12551 files and directories currently installed.)
Preparing to unpack .../lxd-installer_4ubuntu0.1_all.deb ...
Unpacking lxd-installer (4ubuntu0.1) over (4) ...
Setting up lxd-installer (4ubuntu0.1) ...

$ lxc exec u1 -- deluser ubuntu lxd
info: Removing user `ubuntu' from group `lxd' ...

$ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc ls
Unable to trigger the installation of the LXD snap.
Please make sure you're a member of the 'lxd' system group.


This last step shows a clearer error to the user, marking as verified.

** 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 Ubuntu.
https://bugs.launchpad.net/bugs/2061017

Title:
  lxd-installer: permission error not handled and lxd snap not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

** 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-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
  
  Make sure LXD snap is not installed:
  
  $ ! lxc exec u1 -- snap list lxd || false
  error: no matching snaps installed
  
  Remove the LXD group:
  
  $ lxc exec u1 -- delgroup lxd
  warn: The group `lxd' does not exist.
  
  Check lxd-installer version (update to -proposed package if needed):
  
  $ lxc exec u1 -- dpkg -l | grep lxd-installer
  ii  lxd-installer 4 all   
   Wrapper to install lxd snap on demand
  
  Trigger lxd-installer as the regular user not a member of the lxd group:
  
  $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
    File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  Error: Command not found
  
  The output above is the cryptic error that should not be displayed if
  the updated package is installed. Instead, a user not in the lxd group
  that would trigger the lxd-installer, should immediately receive this
  nicer error message:
  
  $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
  Unable to trigger the installation of the LXD snap.
  Please make sure you're a member of the 'lxd' system group.
  
  And the return code should be 1 to indicate an error.
  
  [ Where problems could occur ]
  
  The proposed fix is to check if the /run/lxd-installer.socket socket is
  writable and if not, report a nicer error and exist with an error before
  trying to do the installation and eventually error out.
  
  It is possible for this socket to either be missing or not be writable
  for a reason different than the invoking user not being in the lxd
  group.
  
  If that's the case, the hint to verify the group membership would be
  misleading.
  
  [Original description]
  
  On a fresh install of 24.04 server on Raspberry Pi, I ran 'lxc list'
  without having the lxd snap installed already. There was an attempt to
  install the snap, but it failed, and the snap needed to be manually
  installed:
  
  nr@pi5:~$ lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
    File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  
  More details:
  
  nr@pi5:~$ 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.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=noble
  LOGO=ubuntu-logo
  nr@pi5:~$ apt policy lxd-installer
  lxd-installer:
    Installed: 4
    Candidate: 4
    Version table:
   *** 4 500
  500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
  100 /var/lib/dpkg/status

** Description changed:

  [ Impact ]
  
  * If the LXD group 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.
+ permission denied error and a long delay before complaining the command
+ is not found.
  
  [ Test Plan ]
  
  Create a test instance:
  
  $ lxc launch ubuntu-minimal-daily:24.04 u1
  
  Make sure LXD snap is not installed:
  
  $ ! lxc exec u1 -- snap list lxd || false
  error: no matching snaps installed
  
  Remove the LXD group:
  
  $ lxc exec u1 -- delgroup lxd
  warn: The group `lxd' does not exist.
  
  Check lxd-installer version (update to -proposed package if needed):
  
  $ lxc exec u1 -- dpkg -l | grep lxd-installer
  ii  lxd-installer 4 all   
   Wrapper to install lxd snap on demand
  
  Trigger lxd-installer as the regular user not a member of the lxd group:
  
  $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
    File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  Error: Command not found
  
  The output above is the cryptic error that should not be displayed if
  the updated package is installed. Instead, a user not in the lxd group
  that would trigger the lxd-installer, should immedia

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

** 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
  
  Make sure LXD snap is not installed:
  
  $ ! lxc exec u1 -- snap list lxd || false
  error: no matching snaps installed
  
  Remove the LXD group:
  
  $ lxc exec u1 -- delgroup lxd
  warn: The group `lxd' does not exist.
  
  Check lxd-installer version (update to -proposed package if needed):
  
  $ lxc exec u1 -- dpkg -l | grep lxd-installer
  ii  lxd-installer 4 all   
   Wrapper to install lxd snap on demand
  
  Trigger lxd-installer as the regular user not a member of the lxd group:
  
  $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  Error: Command not found
  
+ 
+ The output above is the cryptic error that should not be displayed if the 
updated package is installed. Instead, a user not in the lxd group triggers the 
lxd-installer, it should receive this nicer error message:
+ 
+ $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
+ Unable to trigger the installation of the LXD snap.
+ Please make sure you're a member of the 'lxd' system group.
+ 
+ And the return code should be 1 to indicate an error.
+ 
  [ Where problems could occur ]
  
- TODO
+ The proposed fix is to check if the /run/lxd-installer.socket socket is
+ writable and if not, report a nicer error and exist with an error before
+ trying to do the installation and eventually error out.
+ 
+ It is possible for this socket to either be missing or not be writable
+ for a reason different than the invoking user not being in the lxd
+ group.
+ 
+ If that's the case, the hint to very the group membership would be
+ misleading.
+ 
  
  [Original description]
  
  On a fresh install of 24.04 server on Raspberry Pi, I ran 'lxc list'
  without having the lxd snap installed already. There was an attempt to
  install the snap, but it failed, and the snap needed to be manually
  installed:
  
  nr@pi5:~$ lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
    File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  
  More details:
  
  nr@pi5:~$ 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.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=noble
  LOGO=ubuntu-logo
  nr@pi5:~$ apt policy lxd-installer
  lxd-installer:
    Installed: 4
    Candidate: 4
    Version table:
   *** 4 500
  500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
  100 /var/lib/dpkg/status

** 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
  
  Make sure LXD snap is not installed:
  
  $ ! lxc exec u1 -- snap list lxd || false
  error: no matching snaps installed
  
  Remove the LXD group:
  
  $ lxc exec u1 -- delgroup lxd
  warn: The group `lxd' does not exist.
  
  Check lxd-installer version (update to -proposed package if needed):
  
  $ lxc exec u1 -- dpkg -l | grep lxd-installer
  ii  lxd-installer 4 all   
   Wrapper to install lxd snap on demand
  
  Trigger lxd-installer as the regular user not a member of the lxd group:
  
  $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
    File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  Error: Command not found
  
- 
- The output above is the cryptic error that should not be displayed if the 
updated package is installed. Instead, a user not in the lxd group triggers the 
lxd-installer, it should receive this nicer error message:
+ The output above is the cryptic error that should not be displayed if
+ the updated package is installed. Instead, a user not in the lxd group
+ that would trigger the lxd-installer, should immediately receive this
+ nicer erro

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

** 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
+ 
+ Make sure LXD snap is not installed:
+ 
+ $ ! lxc exec u1 -- snap list lxd || false
+ error: no matching snaps installed
+ 
+ Remove the LXD group:
+ 
+ $ lxc exec u1 -- delgroup lxd
+ warn: The group `lxd' does not exist.
+ 
+ Check lxd-installer version (update to -proposed package if needed):
+ 
+ $ lxc exec u1 -- dpkg -l | grep lxd-installer
+ ii  lxd-installer 4 all   
   Wrapper to install lxd snap on demand
+ 
+ Trigger lxd-installer as the regular user not a member of the lxd group:
+ 
+ $ lxc exec --user 1000 --group 1000 --env HOME=/home/ubuntu u1 -- lxc list
+ Installing LXD snap, please be patient.
+ Traceback (most recent call last):
+   File "", line 1, in 
+ PermissionError: [Errno 13] Permission denied
+ /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
+ Error: Command not found
+ 
+ [ Where problems could occur ]
+ 
+ TODO
+ 
+ [Original description]
+ 
  On a fresh install of 24.04 server on Raspberry Pi, I ran 'lxc list'
  without having the lxd snap installed already. There was an attempt to
  install the snap, but it failed, and the snap needed to be manually
  installed:
  
  nr@pi5:~$ lxc list
  Installing LXD snap, please be patient.
  Traceback (most recent call last):
-   File "", line 1, in 
+   File "", line 1, in 
  PermissionError: [Errno 13] Permission denied
  /usr/sbin/lxc: 12: exec: /snap/bin/lxc: not found
  
  More details:
  
- nr@pi5:~$ cat /etc/os-release 
+ nr@pi5:~$ 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.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=noble
  LOGO=ubuntu-logo
  nr@pi5:~$ apt policy lxd-installer
  lxd-installer:
-   Installed: 4
-   Candidate: 4
-   Version table:
-  *** 4 500
- 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 4
+   Candidate: 4
+   Version table:
+  *** 4 500
+ 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
+ 100 /var/lib/dpkg/status

-- 
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 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064739] [NEW] linux-image-extra-virtual should depend linux-modules-extra-X.Y.Z-generic

[Simon Déziel]

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/unwanted in VMs.

It would be nice for linux-image-extra-virtual to depend on:

* linux-modules-extra-X.Y.Z-generic


This way, users of VMs wanting more than just the regular set of modules that 
come with linux-image-virtual would simply need to install 
linux-image-extra-virtual to get the versioned dependency on the -extra set of 
modules.

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- linux-image-extra-virtual should not depend on linux-image-generic 
+ linux-image-extra-virtual should depend linux-modules-extra-X.Y.Z-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064739

Title:
  linux-image-extra-virtual should depend linux-modules-
  extra-X.Y.Z-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2064739/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063105] Re: LXD 5.0.3 does not handle root disk sizes in ZFS correctly

[Simon Déziel]

** 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063105

Title:
  LXD 5.0.3 does not handle root disk sizes in ZFS correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/2063105/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064096] Re: rsyslog service timeout on noble numbat

[Simon Déziel]

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 limits.cpu=4 -d 
root,size=32GiB
$ lxc config device add lxd-noble-fde iso-volume disk pool=default 
source=24.04-desktop boot.priority=10
$ lxc config device add lxd-noble-fde tpm tpm
$ lxc start --console=vga lxd-noble-fde

Go through the manual install process but at the "Disk Setup" step, select 
"Erase disk and install Ubuntu" and click "Advanced features...".
Select "Enable hardware-backed full disk encryption" then click "OK"

Once the installation is done, force the LXD VM to stop
$ lxc stop --force lxd-noble-fde

Remove the ISO
$ lxc config device remove lxd-noble-fde iso-volume

Start the VM back
$ lxc start lxd-noble-fde

Once logged in, rsyslog should eventually fail to start and the same
Apparmor denials should show up in `journalctl -k`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064096

Title:
  rsyslog service timeout on noble numbat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040470] Re: Upstream microrelease of squid 5.9

[Simon Déziel]

@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://bugs.launchpad.net/bugs/2040470

Title:
  Upstream microrelease of squid 5.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so

[Simon Déziel]

*** 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 Ubuntu.
https://bugs.launchpad.net/bugs/2063257

Title:
  Noble: default pam config for login tries do load non-existent
  pam_lastlog.so

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063257/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error

[Simon Déziel]

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/stable (5.20
being EOL). Thanks

** Changed in: lxd (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/2057927

Title:
  lxd vga console throws "Operation not permitted" error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063105] Re: LXD 5.0.3 does not handle root disk sizes in ZFS correctly

[Simon Déziel]

@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   PROPERTY  VALUESOURCE
default/virtual-machines/testvm.block  volsize   2404096  local

15 and 16GB are not multiple of 16KiB. You can generally avoid such
issues by defining the storage sizes by using MiB or GiB units. Like
here:

$ lxc config device override testvm root size=15GiB
Device root overridden for testvm
$ lxc config device set testvm root size=16GiB


Could you check if using GiB works for you too? I'll mark the bug as incomplete 
until you can test and report. Thank you.

** Changed in: lxd (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063105

Title:
  LXD 5.0.3 does not handle root disk sizes in ZFS correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2063105/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040459] Re: MRE updates of bind9 for noble

[Simon Déziel]

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 bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040459

Title:
  MRE updates of bind9 for noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind-dyndb-ldap/+bug/2040459/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060965] Re: liblxc is missing in 24.04

[Simon Déziel]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2060965/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062018] Re: [FFe] gnutls28: merge 3.8.5-2 and backport RSAES-PKCS1-v1_5 fix

[Simon Déziel]

> 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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062018

Title:
  [FFe] gnutls28: merge 3.8.5-2 and backport RSAES-PKCS1-v1_5 fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/2062018/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061910] [NEW] lxd-installer should default to pulling LXD from the default channel

[Simon Déziel]

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`
command without first evaluating which snap channel is better for them
based on the upstream doc:
https://documentation.ubuntu.com/lxd/en/latest/installing/#choose-your-
release

Since LXD doesn't allow downgrading, it is best to default to an LTS
version. That is why LXD upstream recently changed the default channel
to be the one pulling LXD 5.21 LTS.

** Affects: lxd-installer (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/2061910

Title:
  lxd-installer should default to pulling LXD from the default channel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061910/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2046379] Re: snapd should depend (!=recommend) on fuse3 for snaps in containers

[Simon Déziel]

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 should depend (!=recommend) on fuse3 for snaps in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2046379/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

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.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
ubuntu@ubuntu:~$ apt policy lxd-installer
lxd-installer:
  Installed: 4
  Candidate: 4
  Version table:
 *** 4 500
500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages
100 /var/lib/dpkg/status

ubuntu@ubuntu:~$ snap list
Name   Version  RevTracking   Publisher   Notes
snapd  2.61.2   21185  latest/stable  canonical✓  snapd

ubuntu@ubuntu:~$ lxc ls
Installing LXD snap, please be patient.
If this is your first time running LXD on this machine, you should also run: 
lxd init
To start your first container, try: lxc launch ubuntu:22.04
Or for a virtual machine: lxc launch ubuntu:22.04 --vm

+--+---+--+--+--+---+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+--+---+--+--+--+---+


ubuntu@ubuntu:~$ snap changes
ID   Status  Spawn   Ready   Summary
1Donetoday at 03:16 UTC  today at 13:50 UTC  Initialize system state
2Donetoday at 13:50 UTC  today at 13:50 UTC  Initialize device
3Donetoday at 14:00 UTC  today at 14:02 UTC  Install "lxd" snap from 
"5.21/stable/ubuntu-24.04" channel

ubuntu@ubuntu:~$ snap list lxd
Name  Version RevTracking   Publisher   Notes
lxd   5.21.1-3f3c2a9  28163  5.21/stable/…  canonical✓  -


The problem seems to be when the invoking user is not a member of the `lxd` 
group which is why there is a Permission denied.

** Changed in: lxd-installer (Ubuntu)
   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/2061017

Title:
  lxd-installer: permission error not handled and lxd snap not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061017] Re: lxd-installer: permission error not handled and lxd snap not installed

[Simon Déziel]

@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 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2061017/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2053192] Re: geoipupdate should be moved to universe

[Simon Déziel]

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/+source/geoipupdate/+bug/2053192/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 795932] Re: ICQ doesn't work since June 10, 2011

[Simon Déziel]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/795932

Title:
  ICQ doesn't work since June 10, 2011

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-haze/+bug/795932/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1052030] Re: Please transition libgnomeprint to multi-arch

[Simon Déziel]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052030

Title:
  Please transition libgnomeprint to multi-arch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnomeprint/+bug/1052030/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054814] Re: lxd-agent-setup cannot be started after a distro upgrade to 24.04

[Simon Déziel]

** 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-agent-setup cannot be started after a distro upgrade to 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058303] Re: lxd-agent-loader might fail on selinux enabled VMs

[Simon Déziel]

** 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-agent-loader might fail on selinux enabled VMs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2058303/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058302] Re: lxd-agent-loader tmpfs too small for some LXD hosts

[Simon Déziel]

** 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-agent-loader tmpfs too small for some LXD hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2058302/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058302] [NEW] lxd-agent-loader tmpfs too small for some LXD hosts

[Simon Déziel]

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 then tentatively copied into any virtual machine instance
where that copy can fail because the tmpfs' size is set to 25MiB:

$ lxc launch ubuntu-minimal-daily:24.04 v1 --vm
Creating v1
Starting v1
$ lxc exec v1 -- mount | grep /run/lxd_agent
tmpfs on /run/lxd_agent type tmpfs 
(rw,nosuid,nodev,noatime,size=25600k,mode=700,inode64)

** Affects: lxd-agent-loader (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/2058302

Title:
  lxd-agent-loader tmpfs too small for some LXD hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2058302/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058303] [NEW] lxd-agent-loader might fail on selinux enabled VMs

[Simon Déziel]

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 because of SELinux labeling issues and typically only kicks-in
after a full re-label.

The particular issue with the agent can be fixed by setting the
appropriate label on the agent binary as part of its creation.

** Affects: lxd-agent-loader (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/2058303

Title:
  lxd-agent-loader might fail on selinux enabled VMs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2058303/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054814] Re: lxd-agent-setup cannot be started after a distro upgrade to 24.04

[Simon Déziel]

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 after a distro upgrade to 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054814] Re: lxd-agent-setup cannot be started after a distro upgrade to 24.04

[Simon Déziel]

** 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-setup cannot be started after a distro upgrade to 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055219] Re: `zpool status` called even if not installed in a container

[Simon Déziel]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055219/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055219] [NEW] `zpool status` called even if not installed in a container

[Simon Déziel]

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 v1 -- apt-get update
lxc exec v1 -- apt-get install -y linux-image-virtual-hwe-22.04
lxc restart v1
sleep 30
lxc exec v1 -- lxd init --auto --storage-backend=zfs
lxc exec v1 -- lxc launch ubuntu-minimal-daily:22.04 c1
lxc exec v1 -- lxc exec c1 -- cloud-init status --long --wait
```

This will output:

```
.
status: done
extended_status: degraded done
boot_status_code: enabled-by-generator
last_update: Tue, 27 Feb 2024 20:59:35 +
detail:
DataSourceLXD
errors: []
recoverable_errors:
WARNING:
- Unable to get zpool status of default: Unexpected error while running 
command. Command: ['zpool', 'status', 'default'] Exit code: - Reason: [Errno 2] 
No such file or directory: b'zpool' Stdout: - Stderr: -
```

This `cloud-init status` returns 0 when running inside a 22.04 instance
but would return 2 when inside a 24.04 instance. See
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2048522 that
changes how warnings influence the return code depending on the OS
version.

** Affects: cloud-init (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/2055219

Title:
  `zpool status` called even if not installed in a container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055219/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961508] Re: Dock displaying over window after resuming from blank screen

[Simon Déziel]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961508

Title:
  Dock displaying over window after resuming from blank screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents

[Simon Déziel]

@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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036127

Title:
  Restarting `systemd-networkd` looses unmanaged bridged parents

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents

[Simon Déziel]

@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/10-netplan-vlan1.network.d/keep_master.conf didn't
work for me. I also tried putting it in 99-netplan-vlan1.network.d to
match the name of my netplan .yaml but still didn't work.


root@networkd-bug:~# cat /etc/netplan/99-vlan1.yaml 
network:
  version: 2
  vlans:
vlan1:
  id: 1
  link: eth0

root@networkd-bug:~# cat 
/etc/systemd/network/99-netplan-vlan1.network.d/keep_master.conf 
[Network]
KeepMaster=true

root@networkd-bug:~# grep -n . /run/systemd/network/*vlan1*
/run/systemd/network/10-netplan-vlan1.netdev:1:[NetDev]
/run/systemd/network/10-netplan-vlan1.netdev:2:Name=vlan1
/run/systemd/network/10-netplan-vlan1.netdev:3:Kind=vlan
/run/systemd/network/10-netplan-vlan1.netdev:5:[VLAN]
/run/systemd/network/10-netplan-vlan1.netdev:6:Id=1
/run/systemd/network/10-netplan-vlan1.network:1:[Match]
/run/systemd/network/10-netplan-vlan1.network:2:Name=vlan1
/run/systemd/network/10-netplan-vlan1.network:4:[Network]
/run/systemd/network/10-netplan-vlan1.network:5:LinkLocalAddressing=ipv6
/run/systemd/network/10-netplan-vlan1.network:6:ConfigureWithoutCarrier=yes

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036127

Title:
  Restarting `systemd-networkd` looses unmanaged bridged parents

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

[Simon Déziel]

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.linuxcontainers.lxd
This means it would do nothing if that virtio-ports device was missing.

On Noble, lxd-agent-loader (0.6) was changed to have udev start lxd-
agent.service only when it sees a virtio-ports LXD knows. Along with
that change, the ConditionPathExists was removed as no longer relevant.


Heinrich did a distro-upgrade moving lxd-agent-loader from 0.5 -> 0.6 but this 
left behind the following symlinks:

```
/etc/systemd/system/multi-user.target.wants/lxd-agent.service
/etc/systemd/system/multi-user.target.wants/lxd-agent-9p.service
```

Causing lxd-agent.service to always want to start, even if the virtio-
ports is not there, thus causing this bug/failure to start lxd-
agent.service.


The fix will be to have the package cleanup the old symlinks left in the 
multi-user.target.wants directory.

-- 
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 on riscv64 6.5.0-9-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1914839] Re: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically

[Simon Déziel]

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 because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1914839

Title:
  package upgrade should replace /etc/ssl/certs/ca-certificates.crt
  atomically

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914839/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 484786] Re: Better support for btrfs snapshots

[Simon Déziel]

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 been
restricted for that reason. The subvolume creation has been restricted
...

I just tested this in a Jammy VM (FYI btrfsctl was replaced by `btrfs
subvolume snapshot`):

```
ubuntu@bj:~$ uname -a
Linux bj 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 
x86_64 x86_64 GNU/Linux
ubuntu@bj:~$ dpkg -l| grep btrfs
ii  btrfs-progs 5.16.2-1
amd64Checksumming Copy on Write Filesystem utilities

ubuntu@bj:~$ mount | grep btrfs
/dev/sda3 on /home type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/)

# Trying while /home is root owned
ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo
Create a snapshot of '/home' in './homefoo'
ERROR: cannot snapshot '/home': Operation not permitted

# Changing ownership of the source subvol
ubuntu@bj:~$ sudo chown ubuntu: /home

# Trying now that /home is owned by ubuntu:
ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo
Create a snapshot of '/home' in './homefoo'
```

So I don't think it's a concern anymore but I won't fiddle with the bug
status and leave that to others ;)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/484786

Title:
  Better support for btrfs snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/484786/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1

[Simon Déziel]

@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 `journalctl -u nginx`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977667

Title:
  package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade:
  installed nginx-core package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1

[Simon Déziel]

@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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977667

Title:
  package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade:
  installed nginx-core package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 359309] Re: mysql client package has broken SSL support

[Simon Déziel]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/359309

Title:
  mysql client package has broken SSL support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/359309/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 779670] Re: The usage of --defaults-file is undocumented in the man

[Simon Déziel]

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 undocumented in the man

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/779670/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs