Merge ~techreed/curtin:storage_eud into curtin:master
Status: | Superseded | ||||
---|---|---|---|---|---|
Proposed branch: | ~techreed/curtin:storage_eud | ||||
Merge into: | curtin:master | ||||
Diff against target: |
24 lines (+2/-1) 2 files modified
curtin/block/schemas.py (+1/-0) curtin/storage_config.py (+1/-1) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ryan Harper (community) | Needs Fixing | ||
Review via email: mp+371429@code.launchpad.net |
This proposal has been superseded by a proposal from 2019-08-18.
Commit message
Allow EUI-64 formatted WWNs for disks and accept NVMe partition naming
Added WWNs matching the EUI-64 format (e.g. eui.00112233445
Altered storage parser to allow partitions named like /dev/nvmeXnXpX. These were previously discarded since the naming scheme does not match traditional HDD/SSD drives.
Description of the change
This branch is the result of installer issues that were encountered while attempting to install Ubuntu Server 18.04.3 LTS on a Samsung 960 EVO M.2 NVMe drive.
The initial issue was that the EUI-64 identifier for the disk was not accepted by curtin as a valid WWN format. After adding this format to the DISK schema and restarting subiquity, curtin recognized the disk and I was able to complete the installation successfully.
While going back to verify that the commit to schemas.py was still working following the initial installation, I encountered a separate issue with curtin's partition parsing.
Since NVMe drives are named like '/dev/nvme0n1' and their partitions are named like '/dev/nvme0n1p1', using lstrip() to get the partition number results in 'p1' instead of '1'. This failed the naming check, the partitions were skipped, and the installer failed because asdict "Couldn't find partition entry in table".
Unmerged commits
- 3af744f... by Reed Slaby <email address hidden>
- 6efeaf4... by Reed Slaby <email address hidden>
- 3af210f... by Reed Slaby <email address hidden>
Hi Reed,
Thanks for the fix! To contribute to curtin, you must sign the Canonical Contributor License Agreement (CLA) [1].
If you have already signed it as an individual, your Launchpad user will be listed in the contributor- agreement- canonical launchpad group [2]. Unfortunately there is no easy way to check if an organization or company you are doing work for has signed. If you are unsure or have questions, email <email address hidden> or ping powersj in #curtin channel via freenode.
For information on how to sign, please see the HACKING document [3]. This links to the cloud-init information but the process is the same for the curtin project.
Thanks again, and please feel free to reach out with any questions.
– www.canonical. com/contributor s /launchpad. net/~contributo r-agreement- canonical/ +members cloudinit. readthedocs. io/en/latest/ topics/ hacking. html
[1] http://
[2] https:/
[3] http://