fstab entry changes breaks bcache/raid/lvm scenarios
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| curtin |
Undecided
|
Unassigned |
Bug Description
Commit 941c43ffff233e5
This change broke/exposed some issues that prevents boot after installation and broken dname symlinks.
Ryan Harper (raharper) wrote : | #1 |
Ryan Harper (raharper) wrote : | #2 |
FAIL: test_fstab (vmtests.
-------
Traceback (most recent call last):
File "/var/lib/
return func(self, *args, **kwargs)
File "/var/lib/
self.
AssertionError: Lists differ: [('/dev/
First list contains 1 additional elements.
First extra element 0:
('/dev/
+ []
- [('/dev/
- '/',
- 'defaults')]
FAIL: test_fstab (vmtests.
-------
Traceback (most recent call last):
File "/var/lib/
return func(self, *args, **kwargs)
File "/var/lib/
expected = self.get_
File "/var/lib/
data_kname = self._dname_
File "/var/lib/
self.
AssertionError: 0 != 1
FAIL: test_fstab (vmtests.
-------
Traceback (most recent call last):
File "/var/lib/
return func(self, *args, **kwargs)
File "/var/lib/
Ryan Harper (raharper) wrote : | #3 |
These issues are fixed by this commit:
https:/
Changed in curtin: | |
status: | New → Fix Committed |
- Handle raid partition lsblk type variance (md or part)
Some verions of lsblk will return TYPE=md or TYPE=part for partitions on top of raid devices. by-id/md- uuid* value. The dname rule to match the device broke.
This means that sometimes /etc/fstab will contain /dev/md0p1 and others the /dev/disk/
- Handle lvm DM_NAME escaping by querying udev
If the LVM logical volume name included a '-' in the name, curtin did not escape this value correctly and the dname symlink referring to the target block device would not show up.