[Group.of.nepali.translators] [Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: open-vm-tools (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: open-vm-tools (Ubuntu Xenial) ** No longer affects: open-vm-tools (Ubuntu Bionic) ** No longer affects: open-vm-tools (Ubuntu Focal) ** No longer affects: open-vm-tools (Ubuntu Groovy) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova Status in cloud-images: In Progress Status in livecd-rootfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Invalid Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in livecd-rootfs source package in Focal: New Status in livecd-rootfs source package in Groovy: New Bug description: with groovy-server-cloudimg-amd64.ova daily build, when only deploy OVA and don't power on VM, the VMTools status is "toolsNotInstalled" But in fact, we have installed open-vm-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1569237] Re: vagrant xenial box is not provided with vagrant/vagrant username and password
** No longer affects: cloud-images/trunk -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1569237 Title: vagrant xenial box is not provided with vagrant/vagrant username and password Status in cloud-images: Fix Released Status in cloud-images xenial series: Fix Released Status in vagrant: Invalid Status in Xenial Backports: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Bug description: It is Vagrant convention that the default user is named "vagrant"[0], and a whole host of scripts assume this to be the default. The xenial box is substantially less useful to Vagrant users with the "ubuntu" user as the default. [0] Search for "user to SSH" in https://www.vagrantup.com/docs/boxes/base.html. Xenial SRU: [impact] * An additional "vagrant" user is available in the created image once the proposed patch is applied. The normal "ubuntu" user is also available, and is conforming to the "ubuntu experience" (it requires cloud-init or another mechanism to be given keys/a password). * The vagrant boxes produced by livecd-rootfs hooks do not conform to the vagrant community's guidelines for box creation, leading vagrant users to use non-official (unaudited) boxes instead, where a "vagrant" user can be found. * A large portion of vagrant automation (3rd party tools, scripts) rely on the presence of a "vagrant" user conforming to the above guidelines. The official ubuntu images are ones of the very few not conforming to the expected user layout. * The official Ubuntu trusty image previously offered a "vagrant" user, and that was lost or omitted when migrating xenial+ to a new build system. This could be considered a regression, although historical context of that change is unfortunately not available anymore. [test case] From a fresh Ubuntu install: * sudo apt install vagrant * vagrant init ubuntu/xenial64 * vagrant up * vagrant ssh notice the user being logged in as is "ubuntu" With either ubuntu/artful64 or ubuntu/trusty64, the same steps log the user in as "vagrant". An image with the proposed changes was built and uploaded as "tribaal/xenial64". [Regression potential] * Users who worked around this behavior in their automation are the most at-risk. They might not be able to login to their boxes anymore, if they worked around by extracting the ubuntu password from the box metadata. If they worked around the problem using cloud-init, no regression will be visible. * The changes introduce a new insecure user, users having worked around the problem on their own might be be unaware of this. * The general consensus in the vagrant community is to install third- party boxes instead of spending time to try and workaround the problems with the official ubuntu boxes, so it is likely to be a limited real-world impact. * The change might affect exotic systems where people for some reason decided to build a non-vagrant machine out of our official vagrant image Note that these regressions will apply to users upgrading their installations to future releases (artful, bionic, and later). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1569237/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1874834] Re: Xenial builds with core18-based snaps pre-seed core snap instead
** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Robert C Jennings (rcj) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1874834 Title: Xenial builds with core18-based snaps pre-seed core snap instead Status in livecd-rootfs package in Ubuntu: New Status in livecd-rootfs source package in Xenial: New Bug description: [Impact] * A xenial image that preseeds a snap based on core18 will end up with core instead and preseeding on boot will fail. [Test Case] * Add a binary hook that pre-seeds lxd (which recently moved to a core18 base). Ensure the snapd and core18 are pulled in by the build and core is not present. Boot the image and ensure pre-seeding is successful. [Regression Potential] * Images with pre-seeded snaps regress in some fashion. We will need to check these builds but there are no pre-seeded snaps in the livecd-rootfs tree for Xenial so this is a low risk change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1874834/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1863024] Re: SRU: bootable buildd images for all releases
** No longer affects: livecd-rootfs (Ubuntu Eoan) ** Merge proposal unlinked: https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378931 ** Merge proposal linked: https://code.launchpad.net/~codyshepherd/livecd-rootfs/+git/livecd-rootfs/+merge/378975 ** Description changed: - We want to backport bootable enabling bootable buildd images to eoan, - bionic, and xenial. + We want to backport bootable enabling bootable buildd images to bionic + and xenial. [Impact] * We don't have bootable buildd images, and we need them for Multipass. [Test Case] * Perform livefs build with project ubuntu-base and subproject buildd * Boot .img file using Multipass, confirm it boots * Perform a livecd-rootfs build using the generated buildd lxd tarball [Regression Potential] * Break existing artifacts in the buildd subproject * Cause buildd subproject to fail to build [Other Info] * None -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1863024 Title: SRU: bootable buildd images for all releases Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Bug description: We want to backport bootable enabling bootable buildd images to bionic and xenial. [Impact] * We don't have bootable buildd images, and we need them for Multipass. [Test Case] * Perform livefs build with project ubuntu-base and subproject buildd * Boot .img file using Multipass, confirm it boots * Perform a livecd-rootfs build using the generated buildd lxd tarball [Regression Potential] * Break existing artifacts in the buildd subproject * Cause buildd subproject to fail to build [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1864252] Re: preseeded snap installs fail in images
** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1864252 Title: preseeded snap installs fail in images Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Status in livecd-rootfs source package in Bionic: Confirmed Status in livecd-rootfs source package in Eoan: Confirmed Bug description: [Impact] Images built with pre-seeded snaps contain insufficient assertion data causing boot to fail. The snaps for seeding are downloaded with a custom snap tool for an earlier cohort API (now deprecated). The assertions that it pulls are incomplete. We could update that list and move to the new API but at this time the snap-tool provides no value compared to use of the snap CLI (cohort support has moved to the cli as well). The development overhead of maintaining snap-tool in livecd-rootfs are not warranted. This patch removes the bespoke snap-tool and relies on the snap CLI instead. [Test Case] * Produce images that include preseeded snaps (in /var/lib/snapd/seed/*) * Boot the resulting image and ensure that the snapd.seeded unit is successful and the snaps (from the correct channels) show up in 'snap list' [Regression Potential] * The interface for these two tools is consistent and the output should be the same. There's always a chance that snap-tool had quirks which a move to the snap CLI uncovers, where the result would be different snaps seeded from before the change. An example would be channel differences before and after this change. I haven't seen issues in my testing and I do think it's unlikely, mostly I'm suspicious of SRUs that don't list any regression potentials. [Other Info] * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions. The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used. The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding. * The attached MP for Xenial is simpler as it never had snap-tool. The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1864252/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829938] Re: [SRU] Support parallel builds for the ubuntu-cpc project
** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829938 Title: [SRU] Support parallel builds for the ubuntu-cpc project Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Cosmic: Fix Released Bug description: [Impact] Individual image builds need to be broken out for the ubuntu-cpc project to allow for build parallelization. This feature exists for eoan and disco. [Test Case] Build all image targets for all architectures and ensure consistent output compared to existing build output: * Ensure that manifests are the same before and after this change for the 'all' target * Build all image targets: * Ensure that all expected hooks are run within the context of each target * Ensure consistent output between those individual targets and the output prior to the change [Regression Potential] This is not without significant risk for the ubuntu-cpc project and requires that rigorous testing be performed to address that risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1829938/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1847300] Re: [backport] magic-proxy: dump proxy log to stdout on failure
** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1847300 Title: [backport] magic-proxy: dump proxy log to stdout on failure Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Disco: Fix Released Bug description: [Impact] When we encounter a failure in 'lb binary' the launchpad builders can only surface the build output from stdout. If the binary hook failure implicates the archive we can not determine fault without the apt proxy log. Backporting the patch from eoan will dump the proxy log to stdout to aid in debugging these failures. [Test case] Run a build with a $REPO_SNAPSHOT_STAMP and a binary hook with 'exit 1'. The apt proxy log should end up on stdout. [Regression Potential] Nearly none. This dumps a file to stdout in the failure exit path; a failure at this stage does not change the outcome of the build. [Other Info] We are seeing issues today in builds that need this debug output in place, we would like to move this SRU through quickly. The code has been running in eoan for at least a week without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1847300/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds
** Also affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1792905 Title: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds Status in cloud-images: Triaged Status in MAAS: Triaged Status in cloud-initramfs-tools package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in open-iscsi package in Ubuntu: Confirmed Status in cloud-initramfs-tools source package in Xenial: New Status in livecd-rootfs source package in Xenial: Invalid Status in open-iscsi source package in Xenial: Confirmed Status in cloud-initramfs-tools source package in Bionic: New Status in livecd-rootfs source package in Bionic: New Status in open-iscsi source package in Bionic: Confirmed Status in cloud-initramfs-tools source package in Cosmic: New Status in livecd-rootfs source package in Cosmic: New Status in open-iscsi source package in Cosmic: Confirmed Bug description: [Impact] * Affects environments where the base image is read-only but kernel modules are copied from the initramfs to the real root via cloud- initramfs-copymods package. * This affects users of our stable release images available from http ://cloud-images.ubuntu.com. * The attached fixes ensure /lib/modules always exists by creating it explicitly instead of relying on it to come from a package. [Test Case] * Download http://cloud-images.ubuntu.com/bionic/current/bionic- server-cloudimg-amd64.squashfs * Unpack it via `sudo unsquashfs bionic-server-cloudimg- amd64.squashfs` * Inspect the unpacked root filesystem and find that '/lib/modules' is missing. * Install local build scripts as described at https://github.com/chrisglass/ubuntu-old-fashioned (note: you will need ubuntu-old-fashioned master for cosmic) * Re-build the images using the updated livecd-rootfs package. * Unpack the resulting livecd.ubuntu-cpc.squashfs artifact using unsquashfs again. * Inspect the unpacked root filesystem and find that '/lib/modules' exists. * It is pure luck that package purges which are done analogously in Cosmic image builds do not remove '/lib/modules', hence this fix is introduced there, as well. * Xenial is not affected. * Test builds were carried out for Cosmic and Bionic with the expected results. [Regression Potential] * This is a fix to a regression. The existence of the directory had previously been ensured, but the mkdir call got lost in recent re- factoring. See also: https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic- proposed/revision/1678 https://bazaar.launchpad.net/~ubuntu-core-dev/livecd- rootfs/trunk/revision/1681 * Packaging tools should not take offense at the existence of a directory, even if it was not part of a package. So potential for unforseeable regressions is very low. ===ORIGINAL BUG DESCRIPTION=== Let me first start with saying MAAS is *not* using iSCSI anymore and is *NOT* in this case either. For some reason now using enlistment, commissioning, and deploying the ephemeral environment will block for 1 min 30 seconds waiting for the iSCSI daemon to succeed, which it never does. This increases the boot time drastically. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1792905/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775710] Re: snap preseeding in xenial not working
** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775710 Title: snap preseeding in xenial not working Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Bug description: [Impact] Customized images built for 16.04 with preseeded snaps fail. [Test case] 1) Install livecd-rootfs 2) Take a copy of the code tree for livecd-rootfs. 3) Prepare a project/subproject tree for hooks: $ mkdir -p live-build/xyz/hooks/ $ echo < live-build/ubuntu-cpc/hooks/000-snap-preseed.binary #!/bin/sh . config/binary . config/functions.snaps snap_preseed chroot telegram EOF 3) Build the image using livecd-rootfs: $ PROJECT=ubuntu-cpc SUBPROJECT=snapped lb config $ PROJECT=ubuntu-cpc SUBPROJECT=snapped lb build 4) Validate that the image contains the preseeded snap as intended from stable/ubuntu-16.04 channel. [Regression potential] --- Snap preseeding released in 2.408.31 (bug #1771177) is incomplete. * Preseeding without specifying a channel will result in a build-break as distro-info is not installed in the build environment * Building with the ubuntu-cpc project overwrites the 'functions' file that added snap functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1775710/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1733353] Re: [SRU] Please accept hibagent to Xenial and Trusty
** Also affects: cloud-images Importance: Undecided Status: New ** Also affects: cloud-images/bb-series Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1733353 Title: [SRU] Please accept hibagent to Xenial and Trusty Status in cloud-images: New Status in cloud-images bb-series series: New Status in hibagent package in Ubuntu: Fix Released Status in hibagent source package in Trusty: Fix Released Status in hibagent source package in Xenial: Fix Released Bug description: [Impact] The package is new to the releases and adds EC2 instances ability to hibernate on an external trigger. [Test Case] Please perform piuparts-like tests with the package and make sure that hibagent service is not started upon the first install or upgrade. Only running the shipped enable-ec2-spot-hibernation command should enable the service and it should be kept enabled during package updates. The package needs kernel support and on generic systems the service tries to start but fail with error. [Regression Potential] Since the package is new it may not cause regressions by being broken but it should not be enabled by default. Accidentally having it enabled would be considered a regression because it would allow triggering hibernation on a system remotely. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1733353/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft
** Branch linked: lp:~rcj/livecd-rootfs/trusty-proposed_ubuntu-cpc ** Changed in: livecd-rootfs (Ubuntu Trusty) Status: Invalid => New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1637290 Title: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in grub2 source package in Precise: New Status in grub2-signed source package in Precise: New Status in livecd-rootfs source package in Precise: Invalid Status in shim source package in Precise: New Status in shim-signed source package in Precise: New Status in grub2 source package in Trusty: In Progress Status in grub2-signed source package in Trusty: In Progress Status in livecd-rootfs source package in Trusty: New Status in shim source package in Trusty: In Progress Status in shim-signed source package in Trusty: In Progress Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in shim source package in Xenial: Fix Committed Status in shim-signed source package in Xenial: Fix Released Status in grub2 source package in Yakkety: Fix Released Status in grub2-signed source package in Yakkety: Fix Released Status in livecd-rootfs source package in Yakkety: Fix Released Status in shim source package in Yakkety: In Progress Status in shim-signed source package in Yakkety: Fix Released Bug description: [Impact] We might want to boot securely one of these days. [Test case] 1) Upgrading - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Verify that the new shimx64.efi file is under /boot/efi/EFI/ubuntu, along with mmx64.efi and fbx64.efi. - Verify that /boot/efi/EFI/ubuntu/MokManager.efi no longer exists. - Verify that trying to apt install grub alone, or apt install shim alone, pulls in the correct matching versions of packages and gives the same results. 2) Booting normally - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system, with Secure Boot enabled. - Verify it boots successfully to the login prompt. - There should be no messages about "Verification failure" or other errors before the kernel is loaded. 3) Network boot. - Update to shim signed and grub2 signed EFI binaries on the TFTP server used. - Verify that a network booting system still boots normally through shim and grub, reaching a login prompt. 4) BootEntry options - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Update or install fwupdate. - Verify that new updates can be applied via fwupdate, that when an update is available, fwupdate will correctly start, apply the update, and reboot to shim normally, leading to a working system. 5) live builds - confirm that the new version of livecd-rootfs has been published to -updates first, and that a daily build of the UEFI-enabled cloud images succeeds with the new shim filenames. [Regression Potential] Any failure to load the kernel from grub, or for shim to load grub, or for the system firmware to load shim (such as "Verification failure" messages) or failure to retrieve or parse BootEntry extended options (such as necessary to load MokManager or fwupdate) should be considered regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1637290/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1683878] Re: blkfront: add uevent for size change
** Also affects: cloud-images Importance: Undecided Status: New ** Also affects: cloud-images/x-series Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1683878 Title: blkfront: add uevent for size change Status in cloud-images: New Status in cloud-images x-series series: New Status in linux package in Ubuntu: Triaged Status in linux-aws package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: In Progress Bug description: A Xen blkfront(xen-blkfront:) patch has been submitted upstream, regarding the resizing of a blkfront device from dom0. This patch would emit a KOBJ_CHANGE uevent, to notify a guest of the change. This allows for custom udev rules, such as automatically resizing a filesystem, when an event occurs. We are requesting that this patch be cherry-picked/backported to the supported Ubuntu kernels. Reference: https://patchwork.kernel.org/patch/9676017/ Reference: https://lkml.org/lkml/2017/4/11/736 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1683878/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
