[Bug 1983599] [NEW] RISC-V cloud images FTBFS after recent StarFive/Nezha changes

[Łukasz Zemczak]

Public bug reported:

[Impact]

When adding the new RISC-V platforms, some of the generic non-SUBARCH
code went missing and some invalid assumptions have been made
(forgetting that we're building RISC-V images that have no SUBARCH),
causing cloud images to fail building. So this is basically a fix for an
updates regression.

[Test Case]

 * Build all our preinstalled RISC-V images with PROPOSED=1 via cdimage and make sure those images build and boot correctly:
   - unleashed
   - starfive
   - nezha
 * Ask the CPC team to build a proposed-enabled cloud image for RISC-V and confirm that it builds correctly

[Regression Potential]

The fix here can cause same kind of regressions, so it can cause other
existing RISC-V images to either not build correctly or build unbootable
images (test case checks that). A general check of all cloud images
could be good, since you never know if we didn't break something outside
of the RISC-V use case (highly unlikely though).

** Affects: livecd-rootfs (Ubuntu)
     Importance: Critical
     Assignee: Łukasz Zemczak (sil2100)
         Status: Fix Released

** Affects: livecd-rootfs (Ubuntu Jammy)
     Importance: Critical
     Assignee: Łukasz Zemczak (sil2100)
         Status: In Progress

** Also affects: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided => Critical

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu Jammy)
       Status: New => In Progress

** Changed in: livecd-rootfs (Ubuntu Jammy)
     Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  RISC-V cloud images FTBFS after recent StarFive/Nezha changes

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  In Progress

Bug description:
  [Impact]

  When adding the new RISC-V platforms, some of the generic non-SUBARCH
  code went missing and some invalid assumptions have been made
  (forgetting that we're building RISC-V images that have no SUBARCH),
  causing cloud images to fail building. So this is basically a fix for
  an updates regression.

  [Test Case]

   * Build all our preinstalled RISC-V images with PROPOSED=1 via cdimage and make sure those images build and boot correctly:
     - unleashed
     - starfive
     - nezha
   * Ask the CPC team to build a proposed-enabled cloud image for RISC-V and confirm that it builds correctly

  [Regression Potential]

  The fix here can cause same kind of regressions, so it can cause other
  existing RISC-V images to either not build correctly or build
  unbootable images (test case checks that). A general check of all
  cloud images could be good, since you never know if we didn't break
  something outside of the RISC-V use case (highly unlikely though).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1983599/+subscriptions