** Summary changed:
- noble minimal cloud images don't have mdadm package installed Edit
+ noble minimal cloud images don't have mdadm package installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
Public bug reported:
noble minimal cloud images don't have mdadm installed.
This is a regression from jammy where the package was a part of minimal images.
For ex. see noble download image manifest[0] vs jammy download image
manifest[1].
This is likely a bug in the ubuntu-cloud-minimal package.
Public bug reported:
noble minimal cloud images don't have sosreport installed.
This is a regression from jammy where the package was a part of minimal images.
For ex. see noble download image manifest[0] vs jammy download image
manifest[1].
This is likely a bug in the ubuntu-cloud-minimal packag
Public bug reported:
"systemctl status ssh" and "systemctl status sshd" both work in jammy, but only
"systemctl status ssh" works in noble.
Expected behavior is that "systemctl status sshd" should work on noble too.
The ssh.service file contains "Alias=sshd.service" but this does not seem to be
Issue was reproducible on jammy generic[0] and kvm[1] download images
too.
Generic download image
```
$ sudo apt install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following
** Attachment added: "apport file"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078720/+attachment/5812724/+files/apport.ubuntu-release-upgrader-core.5vja_xtr.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "Uploading the required dist-upgrade information"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2078720/+attachment/5812723/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Description changed:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst testing
this upgrade path.
Upgrading and later rebooting a jammy GCP instance results in
`linux-headers-6.5.0-1025-gcp`
Public bug reported:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst testing
this upgrade path.
Upgrading and later rebooting a jammy GCP instance results in
`linux-headers-6.5.0-1025-gcp` being
I have tested the package in proposed. The test was done by building a
GCE image with the linux-gcp-edge kernel using livecd-rootfs from
proposed. Confirmed the following:
```
$ uname -r
6.8.0-1012-gcp
$ snap debug seeding
seeded:true
preseeded: true
image-preseeding: 12.545s
@utkarsh mentioned he was looking into the s390x autopkgtest failure.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hi Bryce,
Addressing your feedback per point from comment #12
0. I have put an MP for review[0] instead of a debdiff for this iteration.
Please let me know if that's the appropriate way to propose changes to server
packages. git-ubuntu is definitely on my list to learn now.
1. I concur with this
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
- justification for backporting the fix to the stable release.
+ Currently, the default chrony.conf configures a set of pools. If a user
wishes to use only a specific server/server pool or not use the d
Hello Andreas,
The CPC jammy and mantic fork of livecd-rootfs have been patched with the fix
for this bug since 30 April 2024. Since then CPC have built and tested several
images with the patched CPC livecd-rootfs fork.
As a part of our testing we run an automated test that follows the steps lis
@racb RE comment #4
As far as I understand the only reason the jammy approval should block on
mantic approval is that the approvals must happen in the order of releases with
later release being before an older release.
--
You received this bug notification because you are a member of Ubuntu
Bug
Hi Bryce,
Apologies for the delay in responding.
Thank you for your review comments I'll try to address them in my next fix
proposal.
With respect to the suggesstion you shared about handling well known cases I'll
give it some thought myself , discuss it within my squad, gather feedback and
re
** Description changed:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced a new AppArmor profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and ne
This bug also affects the mantic 6.5 kernel.
** Summary changed:
- AppArmor profile policy `unconfined_restrictions` missing for jammy 6.5 kernel
+ AppArmor profile policy `unconfined_restrictions` missing for jammy and
mantic 6.5 kernel
--
You received this bug notification because you are a
** Description changed:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
- A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced AppArmor new profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and need
Public bug reported:
A CPC snap preseeding test failure on arm64 is blocking image pulication.
A recent update, specifically 6.5.0.1017.17~22.04.1, to the jammy 6.5 kernel
introduced AppArmor new profile `unconfined_restrictions`. This is not
reflected in the snap preseeding code and needs to be
20 matches
Mail list logo
