Comment 5 for bug 686832

I can verify that this fixes the issue.

ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 32 Jan 18 14:21 06eacbef-a3c2-4888-b9e8-faef800781cc -> ../../mapper/222dc0001550218ffp1
lrwxrwxrwx 1 root root 36 Jan 18 14:21 54c316e3-d875-42ae-88d1-451a9876f91e -> ../../mapper/2229a000155fe296e-part1
lrwxrwxrwx 1 root root 32 Jan 18 14:21 9acd1309-5946-48c5-8c9e-e56944494f0b -> ../../mapper/222710001553137dep1
lrwxrwxrwx 1 root root 36 Jan 18 14:21 BC2C-8741 -> ../../mapper/222eb0001559a8c3f-part1
lrwxrwxrwx 1 root root 36 Jan 18 14:21 ca8a7948-d069-4227-8e1d-31d22c5703fa -> ../../mapper/222ca000155636d68-part1

No "failed: Device or resource busy" found in the logs after booting with the fixed package.