curtin doesn't support arm64-efi targets
Bug #1447834 reported by
dann frazier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Undecided
|
Unassigned | ||
curtin (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Curtin doesn't support UEFI-based ARM64 systems.
[Test Case]
Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS incorporating this MP:
https:/
[Regression Risk]
2/3 of the curtin changes are preventing code that was running on all aarch64 platforms to just running on non-UEFI aarch64 systems. Since we only supported non-UEFI systems before, that should be a low risk of regression.
The only other change is adding the grub target name for arm64, which is also pretty straightforward.
Related branches
lp:~dannf/curtin/lp1447834
- Newell Jensen (community): Approve
- curtin developers: Pending requested
-
Diff: 49 lines (+12/-5)3 files modifiedcurtin/commands/block_meta.py (+2/-1)
curtin/commands/curthooks.py (+2/-1)
helpers/common (+8/-3)
Changed in curtin: | |
status: | New → In Progress |
Changed in curtin: | |
status: | In Progress → Fix Committed |
Changed in curtin (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
Hello dann, or anyone else affected,
Accepted curtin into trusty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ curtin/ 0.1.0~bzr221- 0ubuntu1~ 14.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!