curtin fails to partition software raid md0
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| curtin |
Fix Released
|
Medium
|
Unassigned | ||
| curtin (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Xenial |
Fix Released
|
Medium
|
Unassigned | ||
| Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
| Zesty |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
----- Begin SRU Template -----
[Impact]
Curtin is unable to partition md (raid) devices.
A system configured to put partitions on a raided device will fail to
install.
[Test Case]
We added 2 test paths for this code to curtin
a.) unit tests - these will run in the build process, so successful build
verifies that this has passed.
b.) vmtests named: *MirrorbootPart
vmtests are currently only run on trunk, but we can modify source
to run with the packaged version. So, then to test the md path
with a vm install, we will:
i) run a xenial system
ii) enable proposed
iii) install curtin
iv) run vmtests of the Mirrorboot tests using curtin from the sru.
[Regression Potential]
Quite low, the path for failure would be if there were some cases
when the device name for a mdadm partition was /dev/mdNM rather than
/dev/mdNpM.
[Other Info]
The upstream merge proposal is at
https:/
and shows the code that went in to fix this.
----- End SRU Template -----
It seem curtin has problem with software RAID partitioning: md*
Trying to deploy node in MAAS Version 2.0.0+bzr5189-
During partitioning stage curtin returns following error:
An error occured handling 'md0-part1': OSError - could not get path to dev from kname: md01
finish: cmd-install/
finish: cmd-install/
Traceback (most recent call last):
File "/curtin/
ret = args.func(args)
File "/curtin/
meta_
File "/curtin/
handler(
File "/curtin/
get_
File "/curtin/
volume_path = block.kname_
File "/curtin/
raise OSError('could not get path to dev from kname: {}'.format(kname))
OSError: could not get path to dev from kname: md01
could not get path to dev from kname: md01
builtin command failed
finish: cmd-install/
builtin took 8.861 seconds
I've added commit which fixes mentioned error: http://
Related branches
- Scott Moser (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 169 lines (+124/-1)4 files modifiedcurtin/block/__init__.py (+1/-1)
examples/tests/mirrorboot-msdos-partition.yaml (+82/-0)
tests/unittests/test_block.py (+2/-0)
tests/vmtests/test_mdadm_bcache.py (+39/-0)
- Ryan Harper (community): Approve
- Scott Moser: Pending requested
-
Diff: 1365 lines (+661/-168)24 files modifiedcurtin/block/__init__.py (+1/-1)
curtin/commands/apt_config.py (+16/-6)
curtin/commands/block_meta.py (+1/-2)
curtin/commands/curthooks.py (+28/-1)
curtin/deps/__init__.py (+11/-2)
curtin/util.py (+15/-6)
debian/changelog (+20/-0)
debian/new-upstream-snapshot (+47/-3)
examples/tests/centos_basic.yaml (+13/-0)
examples/tests/mirrorboot-msdos-partition.yaml (+82/-0)
helpers/list-flash-kernel-packages (+13/-0)
tests/unittests/test_apt_source.py (+1/-0)
tests/unittests/test_block.py (+2/-0)
tests/unittests/test_curthooks.py (+134/-0)
tests/vmtests/__init__.py (+83/-102)
tests/vmtests/helpers.py (+20/-8)
tests/vmtests/image_sync.py (+31/-17)
tests/vmtests/releases.py (+38/-10)
tests/vmtests/test_apt_config_cmd.py (+4/-0)
tests/vmtests/test_centos_basic.py (+42/-0)
tests/vmtests/test_mdadm_bcache.py (+39/-0)
tests/vmtests/test_raid5_bcache.py (+2/-1)
tools/vmtest-sync-images (+15/-6)
tools/xkvm (+3/-3)
| Ruslan Lutsenko (ruslan-lutcenko) wrote | #1 |
| Changed in curtin: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in curtin (Ubuntu Zesty): | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
| Changed in curtin (Ubuntu Yakkety): | |
| status: | New → Triaged |
| Changed in curtin (Ubuntu Xenial): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in curtin (Ubuntu Yakkety): | |
| importance: | Undecided → Medium |
| description: | updated |
| Łukasz Zemczak (sil2100) wrote Please test proposed package | #2 |
| Changed in curtin (Ubuntu Yakkety): | |
| status: | Triaged → Fix Committed |
| tags: | added: verification-needed |
| tags: |
added: verification-needed-xenial verification-needed-yakkety removed: verification-needed |
| Changed in curtin (Ubuntu Xenial): | |
| status: | Triaged → Fix Committed |
| Scott Moser (smoser) wrote | #3 |
| Scott Moser (smoser) wrote | #4 |
| tags: |
added: verification-done-xenial verification-done-yakkety removed: verification-needed-xenial verification-needed-yakkety |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in curtin (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Robie Basak (racb) wrote Update Released | #6 |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in curtin (Ubuntu Yakkety): | |
| status: | Fix Committed → Fix Released |
| Scott Moser (smoser) wrote Fixed in Curtin 17.1 | #8 |
| Changed in curtin: | |
| status: | Confirmed → Fix Released |
Hello Ruslan, or anyone else affected,
Accepted curtin into yakkety-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
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-
Further information regarding the verification process can be found at https:/