[Bug 1305199] [NEW] Misc Kickseed raid handling problems.

[Max]

Public bug reported:

Misc Kickseed raid handling problems

- The RAID line is ignored when the line has a fstype parameter like:

raid /boot --fstype ext2 --device md0 --level=1 raid.01 raid.02

Probably caused by a missing comma after "spares" here:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/kickseed
/trusty-proposed/view/head:/handlers/raid.sh#L17

- prompt breaking automated installations: "Before RAID can be
configured, the changes have to be written to the storage devices"

Seems to be solved by adding:

preseed partman-md/device_remove_md boolean true
preseed partman-md/confirm boolean true
preseed partman-md/confirm_nooverwrite boolean true

- fatal error: "An unexpected error occurred while setting up a
preseeded RAID configuration"

It seems the second disk is not being partitioned.

I suspect it to be caused by: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/trusty/kickseed/trusty-
proposed/view/head:/handlers/clearpart.sh#L19

==
ks_preseed d-i partman-auto/disk string /dev/discs/disc0/disc0
==

Think it should be for RAID:

==
ks_preseed d-i partman-auto/disk string /dev/discs/disc0/disc /dev/discs/disc1/disc
ks_preseed d-i partman-auto/method string raid
==

But haven't looked further into that.

** Affects: kickseed (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  Misc Kickseed raid handling problems.

Status in “kickseed” package in Ubuntu:
  New

Bug description:
  Misc Kickseed raid handling problems

  - The RAID line is ignored when the line has a fstype parameter like:

  raid /boot --fstype ext2 --device md0 --level=1 raid.01 raid.02

  Probably caused by a missing comma after "spares" here:
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/kickseed
  /trusty-proposed/view/head:/handlers/raid.sh#L17

  - prompt breaking automated installations: "Before RAID can be
  configured, the changes have to be written to the storage devices"

  Seems to be solved by adding:

  preseed partman-md/device_remove_md boolean true
  preseed partman-md/confirm boolean true
  preseed partman-md/confirm_nooverwrite boolean true

  - fatal error: "An unexpected error occurred while setting up a
  preseeded RAID configuration"

  It seems the second disk is not being partitioned.

  I suspect it to be caused by: http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/kickseed/trusty-
  proposed/view/head:/handlers/clearpart.sh#L19

  ==
  ks_preseed d-i partman-auto/disk string /dev/discs/disc0/disc0
  ==

  Think it should be for RAID:

  ==
  ks_preseed d-i partman-auto/disk string /dev/discs/disc0/disc /dev/discs/disc1/disc
  ks_preseed d-i partman-auto/method string raid
  ==

  But haven't looked further into that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kickseed/+bug/1305199/+subscriptions