[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
This bug was fixed in the package shim - 15.8-0ubuntu1
---
shim (15.8-0ubuntu1) mantic; urgency=medium
* New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
- Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
- Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
- Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
* SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
* SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
* SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
* debian/rules: Update COMMIT_ID
-- Mate Kukri Thu, 25 Jan 2024 08:55:28
+
** Changed in: shim (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: shim-signed (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Released
Status in shim-signed source package in Focal:
Fix Released
Status in shim source package in Jammy:
Fix Released
Status in shim-signed source package in Jammy:
Fix Released
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
This bug was fixed in the package shim-signed - 1.51.4
---
shim-signed (1.51.4) jammy; urgency=medium
* New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
- Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
- Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
- Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
* SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
* SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
* SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
-- Mate Kukri Thu, 04 Apr 2024 13:54:55
+0100
** Changed in: shim (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Released
Status in shim-signed source package in Focal:
Fix Released
Status in shim source package in Jammy:
Fix Released
Status in shim-signed source package in Jammy:
Fix Released
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
This bug was fixed in the package shim - 15.8-0ubuntu1
---
shim (15.8-0ubuntu1) mantic; urgency=medium
* New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
- Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
- Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
- Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
* SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
* SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
* SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
* debian/rules: Update COMMIT_ID
-- Mate Kukri Thu, 25 Jan 2024 08:55:28
+
** Changed in: shim-signed (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Released
Status in shim-signed source package in Focal:
Fix Released
Status in shim source package in Jammy:
Fix Released
Status in shim-signed source package in Jammy:
Fix Released
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada
[Canonical-ubuntu-qa] [Bug 2036604] Re: Synchronous Exception when booting VMs via qemu-efi-aarch64
This bug was fixed in the package shim-signed - 1.40.10
---
shim-signed (1.40.10) focal; urgency=medium
* New upstream version 15.8 (LP: #2051151):
- pe: Align section size up to page size for mem attrs (LP: #2036604)
- SBAT level: shim,4
- SBAT policy:
- Latest: "shim,4\ngrub,3\ngrub.debian,4\n"
- Automatic: "shim,2\ngrub,3\ngrub.debian,4\n"
- Note that this does not yet revoke pre NTFS CVE fix GRUB binaries.
* SECURITY UPDATE: a bug in an error message [LP: #2051151]
- mok: fix LogError() invocation
- CVE-2023-40546
* SECURITY UPDATE: out-of-bounds write and UEFI Secure Boot bypass
when booting via HTTP [LP: #2051151]
- avoid incorrectly trusting HTTP headers
- CVE-2023-40547
* SECURITY UPDATE: out-of-bounds write and possible bug [LP: #2051151]
- Fix integer overflow on SBAT section size on 32-bit system
- CVE-2023-40548
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- Authenticode: verify that the signature header is in bounds.
- CVE-2023-40549
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe: Fix an out-of-bound read in verify_buffer_sbat()
- CVE-2023-40550
* SECURITY UPDATE: out-of-bounds read and possible bug [LP: #2051151]
- pe-relocate: Fix bounds check for MZ binaries
- CVE-2023-40551
-- Mate Kukri Thu, 04 Apr 2024 13:56:01
+0100
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/2036604
Title:
Synchronous Exception when booting VMs via qemu-efi-aarch64
Status in cloud-images:
New
Status in autopkgtest package in Ubuntu:
Confirmed
Status in edk2 package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Confirmed
Status in shim package in Ubuntu:
Fix Released
Status in shim-signed package in Ubuntu:
Fix Committed
Status in shim source package in Focal:
Fix Released
Status in shim-signed source package in Focal:
Fix Released
Status in shim source package in Jammy:
Fix Released
Status in shim-signed source package in Jammy:
Fix Released
Status in edk2 package in Debian:
Fix Released
Bug description:
I try to create an autopkgtest VM on an arm64 system with
autopkgtest-buildvm-ubuntu-cloud -v --release mantic
or on an amd64 system with
autopkgtest-buildvm-ubuntu-cloud --arch arm64 -v --release mantic
In both cases I get:
Found linux image: /boot/vmlinuz-6.5.0-5-generic
Found initrd image: /boot/initrd.img-6.5.0-5-generic
Found linux image: /boot/vmlinuz-6.3.0-7-generic
Found initrd image: /boot/initrd.img-6.3.0-7-generic
Found linux image: /boot/vmlinuz-6.2.0-20-generic
Found initrd image: /boot/initrd.img-6.2.0-20-generic
Warning: os-prober will not be executed to detect other bootable partitions.
BdsDxe: loading Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x5,0x0)
Synchronous Exception at 0x5C328000
Synchronous Exception at 0x5C328000
^A^Cqemu-system-aarch64: terminating on signal 2
Traceback (most recent call last):
/var/crash has no entries.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: qemu-system-arm 1:8.0.4+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: pass
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Tue Sep 19 15:37:20 2023
InstallationDate: Installed on 2021-08-17 (763 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210813)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lspci-vt:
-[:00]-+-00.0 NVIDIA Corporation GK208B [GeForce GT 730]
\-00.1 NVIDIA Corporation GK208 HDMI/DP Audio Controller
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: Mar 26 2020
dmi.bios.release: 1.0
dmi.bios.vendor: EFI Development Kit II / Marvell
dmi.bios.version: EDK II
dmi.board.name: Armada 8040 MacchiatoBin
dmi.board.vendor: SolidRun
dmi.board.version: Rev. 1.3
dmi.chassis.type: 2
dmi.chassis.vendor: SolidRun
dmi.chassis.version: Rev. 1.3
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/Marvell:bvrEDKII:bdMar262020:br1.0:svnSolidRun:pnArmada8040MacchiatoBin:pvrRev.1.3:rvnSolidRun:rnArmada8040MacchiatoBin:rvrRev.1.3:cvnSolidRun:ct2:cvrRev.1.3:sku:
dmi.product.name: Armada 8040 MacchiatoBin
dmi.product.ver
[Canonical-ubuntu-qa] [Merge] ubuntu-manual-tests:snap-revisions into ubuntu-manual-tests:main
Tim Andersson has proposed merging ubuntu-manual-tests:snap-revisions into ubuntu-manual-tests:main. Requested reviews: Ubuntu Testcase Admins (ubuntu-testcase) For more details, see: https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/471992 Adds a test case checking the snap revisions after a release upgrade. -- Your team Canonical's Ubuntu QA is subscribed to branch ubuntu-manual-tests:main. diff --git a/testcases/image/1822_Upgrade_Check_Snap_Revisions b/testcases/image/1822_Upgrade_Check_Snap_Revisions new file mode 100644 index 000..4c79d5b --- /dev/null +++ b/testcases/image/1822_Upgrade_Check_Snap_Revisions @@ -0,0 +1,23 @@ +The scope of this test is to ensure that the correct snap tracking is present post release upgrade. + +For this testcase, it's helpful if the tester is in contact with Ubuntu developers on IRC (https://wiki.ubuntu.com/IRC/ChannelList - channel: #ubuntu-release or #ubuntu-quality). Please paste any relevant terminal output in the box below when submitting your test result. + + +Download the iso for the previous LTS release +In a vm, or on hardware, do a basic installation of the previous release +Once installed, and all is up to date, get the `ubuntu-release-upgrader` tar from here: https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader +Ensure you have the relevant version of the release upgrader - it must be the version of the release upgrader for the release you are trying to upgrade to - and take the one from -proposed if there is one +Run the following, and keep the terminal output: +snaps=$(snap list | tail -n +2 | cut -d' ' -f1) +for snap in $snaps; do snap info $snap; done +Go to the directory where the ubuntu-release-upgrader tar is, and run the following: +tar -xf ubuntu-release-upgrader_... +cd ubuntu-release-upgrader/ +Please be aware, at the following step, that you may need additional flags to do-release-upgrade. To garner information on this, please ping on #ubuntu-release on IRC. +./do-release-upgrade +... Wait for the upgrade to finish +Reboot the machine post upgrade. +Run the following, and keep the terminal output: +snaps=$(snap list | tail -n +2 | cut -d' ' -f1) +for snap in $snaps; do snap info $snap; done +If the snap tracking is as desired, submit a pass result. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ubuntu-manual-tests:snap-revisions into ubuntu-manual-tests:main
>If the snap tracking is as desired Perhaps we can add a reference to the desired snap tracking. -- https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/471992 Your team Canonical's Ubuntu QA is subscribed to branch ubuntu-manual-tests:main. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ubuntu-manual-tests:snap-revisions into ubuntu-manual-tests:main
Review: Needs Information Diff comments: > diff --git a/testcases/image/1822_Upgrade_Check_Snap_Revisions > b/testcases/image/1822_Upgrade_Check_Snap_Revisions > new file mode 100644 > index 000..4c79d5b > --- /dev/null > +++ b/testcases/image/1822_Upgrade_Check_Snap_Revisions > @@ -0,0 +1,23 @@ > +The scope of this test is to ensure that the correct snap tracking is > present post release upgrade. > + > +For this testcase, it's helpful if the tester is in contact with Ubuntu > developers on IRC (https://wiki.ubuntu.com/IRC/ChannelList - channel: > #ubuntu-release or #ubuntu-quality). Please paste any relevant terminal > output in the box below when submitting your test result. Why "it's helpful if the tester is in contact with Ubuntu developers"? I suppose the answer is: to know what the expected snap tracking is. But I think there should be a way that does not require asking someone on IRC. > + > + > +Download the iso for the previous LTS release What about upgrades between interim releases? Do we always need the previous LTS? > +In a vm, or on hardware, do a basic installation of the previous > release > +Once installed, and all is up to date, get the > `ubuntu-release-upgrader` tar from here: > https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader > +Ensure you have the relevant version of the release upgrader - > it must be the version of the release upgrader for the release you are trying > to upgrade to - and take the one from -proposed if there is one > +Run the following, and keep the terminal output: > +snaps=$(snap list | tail -n +2 | cut -d' ' -f1) > +for snap in $snaps; do snap info $snap; done > +Go to the directory where the ubuntu-release-upgrader tar is, and > run the following: > +tar -xf ubuntu-release-upgrader_... > +cd ubuntu-release-upgrader/ > +Please be aware, at the following step, that you may need > additional flags to do-release-upgrade. To garner information on this, please > ping on #ubuntu-release on IRC. > +./do-release-upgrade > +... Wait for the upgrade to finish > +Reboot the machine post upgrade. > +Run the following, and keep the terminal output: > +snaps=$(snap list | tail -n +2 | cut -d' ' -f1) > +for snap in $snaps; do snap info $snap; done > +If the snap tracking is as desired, submit a pass result. These tests in general try to make it very clear what the expected outcome is. Here it is difficult to tell... -- https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/471992 Your team Canonical's Ubuntu QA is subscribed to branch ubuntu-manual-tests:main. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
