Comment # 9 on bug 1121720 from Ancor Gonzalez Sosa

(In reply to Pieter Hollants from comment #7)
> I don't think it is a duplicate: by looking at

Yes, this is just another consequence of the very same bug. The same fix that
we already reported for bug#1120979 (adding a slash to the line linked below)
also fixes this other symptom.

https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/autoinst_profile/partition_section.rb#L231

> I deducted that specifying an
> explicit <raid_name> in the <raid_options> section, I could work around the
> other bug #1120979:

Wrong deduction ;-) Reusing a raid was broken either by using /dev/md0 and by
using /dev/md/0. With the fix we already commented in the other bug, both work.

> <drive>
> [...]
>   <raid_name>/dev/md/0</raid_name>
> [...]
> </drive>
> 
> But then I discovered _this_ bug.

Then you rediscovered the same bug. ;-)

> Please also note that by referring to the raid as /dev/md/0 instead of
> /dev/md0 I think we've broken compatibility with existing Autoyast profiles:
> both the Autoyast Documentation for openSUSE 15.0 at
> https://doc.opensuse.org/projects/autoyast/#ay.partition_sw_raid and the
> newest documentation I could find, for SLES 12SP4, use "/dev/md0" as
> <raid_name>.

As said, backwards compatibility is not broken. Once the bug is fixed, it will
work for both /dev/md0 and /dev/md/0.