[Bug 2149919] Re: [SRU] piboot-try is missing definition of Zero 2W

[Dave Jones]

** Summary changed:

- piboot-try is missing definition of Zero 2W
+ [SRU] piboot-try is missing definition of Zero 2W

** Description changed:

+ [ Impact ]
+ 
  The db is missing the Zero 2 W pattern, which results in piboot-try
  thinking the f-k method is not "pi-try" as it should be. This in turn
  breaks the validation service, and flash-kernel execution.
+ 
+ [ Test plan ]
+ 
+ * Flash the Ubuntu Server for Pi image to a spare SD card
+ * Boot the image and login
+ * sudo flash-kernel
+ * Observe failure
+ * Enabled the proposed pocket
+ * sudo apt install flash-kernel
+ * sudo flash-kernel
+ * Observe success
+ * sudo reboot
+ * Ensure system comes back up
+ 
+ [ Where things could go wrong ]
+ 
+ The change is purely additive to the database and thus will not affect
+ other boards. However, anything that messes with piboot-try has the
+ potential to break boot, hence the test plan ensures not only that the
+ primary bug is fixed, but that the boot sequence continues to operate
+ (this will implicitly include testing the A/B boot mechanism as "sudo
+ flash-kernel" installs new "untested" assets which will go through a
+ full test cycle during the reboot).

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

Title:
  [SRU] piboot-try is missing definition of Zero 2W

Status in piboot-try package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

  The db is missing the Zero 2 W pattern, which results in piboot-try
  thinking the f-k method is not "pi-try" as it should be. This in turn
  breaks the validation service, and flash-kernel execution.

  [ Test plan ]

  * Flash the Ubuntu Server for Pi image to a spare SD card
  * Boot the image and login
  * sudo flash-kernel
  * Observe failure
  * Enabled the proposed pocket
  * sudo apt install flash-kernel
  * sudo flash-kernel
  * Observe success
  * sudo reboot
  * Ensure system comes back up

  [ Where things could go wrong ]

  The change is purely additive to the database and thus will not affect
  other boards. However, anything that messes with piboot-try has the
  potential to break boot, hence the test plan ensures not only that the
  primary bug is fixed, but that the boot sequence continues to operate
  (this will implicitly include testing the A/B boot mechanism as "sudo
  flash-kernel" installs new "untested" assets which will go through a
  full test cycle during the reboot).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/piboot-try/+bug/2149919/+subscriptions