Public bug reported:
[Impact]
* Snaps are not included in manifests for those releases where snaps
are pre-seeded (Xenial & Bionic)
* Snaps should appear in the manifests for (mf)diff purposes.
* Note that this issue has been fixed already in Cosmic and newer.
[Test Case]
* Build Xenial o
I tested this by running a test build (using Ubuntu Old Fashioned:
https://github.com/chrisglass/ubuntu-old-fashioned) using the bionic-
proposed branch of livecd-rootfs and all the partner hooks. All images
were built successfully without failures.
--
You received this bug notification because y
I built a minimal image using the -proposed package and tested it by
running it on kvm. There do not appear to be any regressions (the image
boots fine and appears normal). A non-minimal build is in the works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
[Test Case]
- Build Xenial Minimal Image
+ Build Xenial Minimal Image (along with private hook that actually installs
+ the resolvconf package).
Check /etc/res
I have also built and mounted a base (non-minimal) image from xenial-
proposed and confirmed no apparent regressions for the base image as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801134
T
The package and version I tested: livecd-rootfs/xenial-proposed, version
2.408.41 xenial.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
[Test Case]
Build Xenial Minimal Image
Check /etc/resolv.conf and confirm it is a symlink and not a 0-byte file.
+
+ [Regression Potential]
+ Regression wou
Public bug reported:
[Impact]
* grub-efi packages not included in image manifests, manifests
incorrect
[Test Case]
* build bionic (or later) image using ubuntu-cpc hooks;
note that grub-efi packages are installed in the image but not
included in the image package manifest.
[Regressi
** Description changed:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
+
+ [Test Case]
+ Launch VM instance using Xenial Minimal image.
+ Confirm no WAN connectivity/no DNS.
+ `cat /etc/resolv.conf` shows zero-byte file.
--
You recei
** Description changed:
DNS was broken in Xenial minimal images under some circumstances due to
a 0-byte /etc/resolv.conf file.
- [Test Case]
- Launch VM instance using Xenial Minimal image.
- Confirm no WAN connectivity/no DNS.
- `cat /etc/resolv.conf` shows zero-byte file.
+ [Test Case]
Public bug reported:
After completing release upgrade from Eoan to Focal as a devel release
without errors, subsequent updates via Software Updater show a window
that prompts the user for a Partial Upgrade, stating "Not all updates
can be installed.
The user can then either select Partial Upgrade
Public bug reported:
Ubuntu release: 20.04 Focal Fossa
Package version: gnome-shell 3.34.3-1ubuntu1, firefox 72.0.2+build1-0ubuntu1
Expected Behavior: new Terminal window would be foregrounded/focused on
creation via ctrl-alt-t when another terminal window not already focused
Actual Behavior: if
Public bug reported:
On exactly every other reboot, a purple splash screen with the words
"Ubuntu 20.04" and four dots presents itself immediately on boot, and
prevents boot from progressing any further.
This splash screen occurs before the grub menu, and also before the
splash screen presented f
My attempts to verify test case k) seem to indicate there is still a
problem somewhere.
I've verified
i) that grub-legacy-ec2 is no longer in the server seed [1]
iv) that the livecd.ubuntu-cpc.manifest contains grub-legacy-ec2 and
ubuntu-server.
However,
ii) the rootfs manifest has not retaine
Also as to verification of k.i), I've verified that the "deployed"
server seed [1] matches the seed configuration in VCS linked in the last
comment.
[1] https://people.canonical.com/~ubuntu-
archive/seeds/ubuntu.xenial/server
--
You received this bug notification because you are a member of Ubun
My initial guess at why this has failed is that the ubuntu-server
package appears to still depend on grub-legacy-ec2 [1].
[1] https://packages.ubuntu.com/xenial/ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Ok, I wasn't building from -proposed, I'll try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news config into a new package
To manage notifications about this bug g
All parts of case k) verified by repeating the steps described above
against -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news config into a new package
To man
I've built the ubuntu-base/buildd project and verified that the
resulting .img boots in multipass.
Using the lxd tarball to do a build is still pending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
The xenial changes for 2.408.61 are currently failing verification for
me. Depending on the value of the --image-format argument passed to the
livefs build, the build results in either a .img that boots (--image-
format ext4) or lxd/rootfs tarballs that work (--image-format none), but
not both in t
This bug is also affecting Hirsute cloud images. The workaround
mentioned in the comments does seem to alleviate the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910815
Title:
race on boot
I've proposed an MP that lays down a systemd conf file in cloud images
that implements the workaround described in this bug's top comment. This
represents a temporary workaround for cloud images, and can be reverted
if/when it's no longer needed.
--
You received this bug notification because you
Public bug reported:
Ubuntu "bootable" buildd vm images, if imported into lxd and booted in a
VM container, cannot produce an interactive bash session via, e.g. `lxd
exec bash`.
This appears to be a problem of the buildd image lacking grub settings
to produce console output on ttyS0. Lack of con
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863024
Title:
SRU: bootable b
I've built xenial buildd using livecd-rootfs version 2.408.65 and
verified the lxd and rootfs tarballs are sized and structured as
expected, and that the .img boots in multipass. This confirms
verification done for xenial.
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
[Impact]
* There are currently no manifests being produced for buildd tarballs
in bionic and focal.
* Manifests _are_ being produced for the buildd tarballs in Hirsute and
Xenial (the latter as part of recent longer-term work to produce
bootable buildd images in Xenial)
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/397440
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/397441
--
You received this bug notification because you are a memb
** Description changed:
[Impact]
- * There are currently no manifests being produced for buildd tarballs
- in bionic and focal.
+ * There are currently no manifests being produced for buildd tarballs
+ in bionic, focal, and groovy.
- * Manifests _are_ being produced for the buildd tarba
Public bug reported:
[Impact]
* Bootable buildd images are currently built from the -release pocket only,
leaving them vulnerable to issues fixed by -updates and/or -security.
* MP: #387164 [1] should be backported to ensure updated packages are used
when building the bootable buildd ima
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387163
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387162
** Merge proposal linked:
https://code.launchpad.net/~cod
I've verified that this is fixed for Focal by:
* Building the livecd-rootfs 2.664.5 source package in a private ppa
* Building the focal buildd image with the cpc-buildd livefs, with the above
private-ppa as an extra archive
* Booting the resulting disk-linux-virtual.img in Multipass with libvirt
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891061
Title:
SRU: Bootable buildd images boot vu
Public bug reported:
Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for
development work. I run it on a Lenovo X1 Carbon 8th Generation
connected to dual monitors via a Lenovo dock. Both monitors are capable
of outputting sound via HDMI.
I use bluetooth headphones frequently w
So I did look at those options, but disabling them did not provide the
experience I was looking for, and required me to do as much or more
manual switching of audio devices.
To be clear, I don't want to disable the functionality that these
options provide. I am happy with the audio switching to ho
I probably also should have elaborated that this succeeded over multiple
consecutive reboots.
** Changed in: plymouth (Ubuntu Focal)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hi, this appears to be fixed.
I re-enabled "quite splash" in my grub config, ran update-grub, and
rebooted. I got a black splash screen with white "Ubuntu" branding, and
a prompt to enter my FDE key. Boot went just fine.
Thanks!
--
You received this bug notification because you are a member of
Public bug reported:
Placeholder: will update with SRU template
** Affects: python-s3transfer (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/18
** Description changed:
- Placeholder: will update with SRU template
+ Pull in upstream [1] changes to bump this package version to the latest
+ release version (0.3.3) as required by upstream awscli [2].
+
+ [Impact]
+
+ * This bug is intended to work in tandem with bugs for awscli [3] and
+ p
Public bug reported:
[Impact]
* the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
* The various outdated versions in, e.g. xenial and bionic, leave out
lots of useful botocore functionality.
* SRUing the
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: focal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867673
Title:
awscli not kept up to d
This bug affects all suites to some extent, excluding groovy-proposed,
and the package version is more outdated for the older supported
releases, e.g. xenial and bionic.
The versions in the archive for xenial and bionic, 1.11 and 1.14,
respectively, lack functionality applicable to newer AWS featu
** Description changed:
[Impact]
- * the python-botocore package is out of date, and out of sync with
+ * the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
- * The various outdated versions in, e.g
** Description changed:
+ [Original Bug Description]
+
awscli is not kept up to date, and so new AWS features are not
available.
The AWS pip installation method is unaudited and unsigned, and is not a
production ready solution to the out-of-date problem.
The awscli package needs t
** Description changed:
[Impact]
* the python-botocore package is out of date, and out of sync with
python3-botocore in debian [1], for all pockets except groovy-proposed.
* The various outdated versions in, e.g. xenial and bionic, leave out
lots of useful botocore functionality
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387162
** Merge proposal linked:
https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/387163
** Merge proposal linked:
https://code.launchpad.net/~cod
** Changed in: cloud-images
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/1885571
Title:
Can't set boot kernel in GRUB on focal image
To manage notifications about t
Confirmed on Multipass using the 20200702 focal release image. Also
captured a sample selection of virsh console output during the infinite
boot loop: https://paste.ubuntu.com/p/dqqgqryXNV/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
Iscsid restart fails when killed with a SIGTERM.
Conditions:
Iscsid restart policy set to "Always" via a .conf file in
/etc/systemd/system/iscsid.service.d/, with the contents:
[Service]
Restart=always
Steps to Reproduce:
1. Confirm iscsid is running, e.g.
$ ps aux | grep i
** Changed in: livecd-rootfs (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/1805190
Title:
Image manifests for bionic and later are incorrect
To manage no
Hi there. It looks like the fix for this bug for Cosmic is already in
cosmic-proposed: https://code.launchpad.net/~codyshepherd/livecd-rootfs
/uefi-manifests-cosmic/+merge/357833. Just waiting to be uploaded!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please note that for now this bug only applies to cloud images.
** Description changed:
[Impact]
- * Snaps are not included in manifests for those releases where snaps
- are pre-seeded (Xenial & Bionic)
+ * Snaps are not included in manifests for cloud images for those
+ releases where sna
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805497
Title:
Snaps not included in image manifests
To manage noti
Verification done for Bionic and Xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805497
Title:
Snaps not i
Public bug reported:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifica
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
+
+ [Impact]
+
+ * We don't have bootable buildd images, and we need them for Multipass.
+
+ [Test Case]
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
This is a placeholder description: will fill in SRU template soon.
[Impact]
- * We don't have bootable buildd images, and we need them for Multipass.
+ * We don't ha
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
- This is a placeholder description: will fill in SRU template soon.
[Impact]
* We don't have bootable buildd images, and we need them for Multipass.
[Test Case]
** Description changed:
[Impact]
The motd-news script is largely useless for desktop users, as they rarely
login via a text console. It makes more sense for server users.
We can use package dependencies to have the motd-news script enabled on
servers, but disabled on desktops, and still
Public bug reported:
This issue has already been identified and fixed in the (upstream?)
github repository:
https://github.com/ibm-s390-linux/s390-tools/commit/63ff07ba38dda99e2661a097d05266555c727a2e
The issue fixed by the revert linked above is causing Cloudware Oracular
download image builds t
> (But btw. why have you attached your Intel ProcCpuinfoMinimal.txt
here?)
I used ubuntu-bug to file the bug, and it collected that automatically.
It's irrelevant, I've removed it.
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/207236
I've tested this by running an oracular build on s390x with your ppa
package thrown in. The build succeeded, so it looks like the ppa package
is what we want.
Relevant portions from the build log:
```
After this operation, 747 MB of additional disk space will be used.
Get:1 http://ftpmaster.inter
Public bug reported:
[ Impact ]
Several tools rely on the `distro-info` package to tell them which releases are
available.
This package just contains data, with no format changes.
[ Regression Potential ]
Minimal, as long as we are only adding new entries (we do this every
release).
[ Test Ca
I've confirmed on focal, jammy, noble, and oracular that enabling
-proposed and updating distro-info-data causes `distro-info` commands to
output correct info:
--devel and --latest: shows plucky
--fullname: shows Ubuntu 25.04 "Plucky Puffin"
--stable: shows oracular
--lts: shows noble
--series=plu
** Description changed:
[ Impact ]
- * Lack of manifest causes downstream builds to break during the
+ * Lack of manifest causes downstream builds to break during the
manifest copy commands in the qcow binary hook. This is causing jammy
riscv64 builds to fail.
- * proposed fix [1] i
Public bug reported:
[ Impact ]
* Lack of manifest causes downstream builds to break during the
manifest copy commands in the qcow binary hook. This is causing jammy
riscv64 builds to fail.
* proposed fix [1] is to check that $SUBARCH is nonzero in the if
branch that returns early.
[ Test Pla
> Does the solution to this bug include making the SBOMs public @
https://cloud-images.ubuntu.com/ ?
Not exactly. The plan is for SBOMs to be available at the org level for
a variety of artifacts as part of the 25.04 cycle. So SBOMs for cloud
images would be gotten from the same place that e.g. SB
@lool I think the changes have actually landed in -updates. Please
correct me if I'm wrong but I believe this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifest
Oh, nevermind, the changes are still in -proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifest not generated for ubuntu-cpc uefi hook in riscv64 when no
subarch present
T
Hi, I've verified the changes by building a riscv64 image from -proposed
and verified that the image builds successfully. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086455
Title:
manifes
** Changed in: cloud-images
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072929
Title:
Ubuntu cloud image partition numbering
To manage notifications ab
** Changed in: cloud-images
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/2080223
Title:
Ensure WSL instances do not rely on the Windows launcher by using the
ne
Hi. I indeed followed the test plan, using livecd-rootfs version
2.765.54.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done-jammy
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi there, as far as I can tell, pinning docker to 20.x leads to build
failures for riscv64 artifacts, as the 20.x docker.io is not available
for that arch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
74 matches
Mail list logo
