Merge lp:~smoser/curtin/trunk.lp1680591 into lp:~curtin-dev/curtin/trunk
Proposed by
Scott Moser
Status: | Merged |
---|---|
Merged at revision: | 483 |
Proposed branch: | lp:~smoser/curtin/trunk.lp1680591 |
Merge into: | lp:~curtin-dev/curtin/trunk |
Diff against target: |
67 lines (+22/-1) 3 files modified
curtin/commands/block_meta.py (+9/-1) curtin/udev.py (+9/-0) tests/vmtests/test_bcache_basic.py (+4/-0) |
To merge this branch: | bzr merge lp:~smoser/curtin/trunk.lp1680591 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Approve | |
Ryan Harper (community) | Approve | ||
Review via email: mp+322151@code.launchpad.net |
Commit message
Make systems with root on bcache use root=UUID=.
Systems with root on bcache would end up booting with root=/dev/bcache0
(or bcache1). Bcache device names are not guaranteed, so this could
cause issues.
The fix is to invoke 'udevadm trigger' after creating a filesystem on
a bcache device. That will populate /dev/disk/by-uuid, which will
cause grub to properly decide to boot by root=UUID=.
To post a comment you must log in.
This is good. I think we should also document why the udevadm trigger is required. Grub relies upon udevadm information to confirm UUID presense prior to rebooting into a system which may not see the UUID. Separately, udev does not currently *inotify watch* bcache devices like it does other block devs and therefor we do not get an automatic udevadm trigger when mkfs closes a bcache device (like we do with say a partition).