Validation performed as per test plan. Interestingly, the failure case
did *not* fail (the release-upgrader succeeded in calculating a path
that removed flash-kernel, transitioning to piboot-try), but the
proposed case also worked perfectly.

With a far more complicated installed set of packages (an old card I'd
used to backup a desktop install I'd used for a while), the failure case
*did* fail but not in the expected way (failed to calculate upgrade
path, so it wouldn't permit the upgrade to proceed). Meanwhile, the
proposed version succeeded in calculating the upgrade path and again
worked perfectly.

So, the proposed version definitely fixes *some* upgrade path issues,
but we've still no idea how people are winding up in the situation where
the upgrade has succeeded but piboot-try doesn't get installed. Still,
nothing in the proposed version appears to make anything *worse* and it
definitely improves *some* upgrade paths (though evidently not all,
given klatls' comments above), so I'm going to mark the validation done
for resolute.

** Tags removed: verification-needed-resolute
** Tags added: verification-done-resolute

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

Title:
  [SRU] Force switch to piboot-try on Raspberry Pi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2151216/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to