group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #20153
[Bug 1641661] Re: curtin fails to partition software raid md0
This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: curtin
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1641661
Title:
curtin fails to partition software raid md0
Status in curtin:
Fix Released
Status in curtin package in Ubuntu:
Fix Released
Status in curtin source package in Xenial:
Fix Released
Status in curtin source package in Yakkety:
Fix Released
Status in curtin source package in Zesty:
Fix Released
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: *MirrorbootPartitions
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://code.launchpad.net/~raharper/curtin/trunk.lp1641661/+merge/311275
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-0ubuntu1 (16.04.1).
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/stage-partitioning/builtin/cmd-block-meta: FAIL: failed: configuring partition: md0-part1
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: failed: curtin command block-meta
Traceback (most recent call last):
File "/curtin/curtin/commands/main.py", line 211, in main
ret = args.func(args)
File "/curtin/curtin/commands/block_meta.py", line 62, in block_meta
meta_custom(args)
File "/curtin/curtin/commands/block_meta.py", line 1041, in meta_custom
handler(command, storage_config_dict)
File "/curtin/curtin/commands/block_meta.py", line 550, in partition_handler
get_path_to_storage_volume(info.get('id'), storage_config),
File "/curtin/curtin/commands/block_meta.py", line 267, in get_path_to_storage_volume
volume_path = block.kname_to_path(partition_kname)
File "/curtin/curtin/block/__init__.py", line 114, in kname_to_path
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/stage-partitioning/builtin: FAIL: failed: running 'curtin block-meta custom'
builtin took 8.861 seconds
I've added commit which fixes mentioned error:
http://bazaar.launchpad.net/~ruslan-
lutcenko/curtin/curtin/revision/431
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1641661/+subscriptions