Comment 13 for bug 1780332

I'm not sure what vaultlocker is.

trigger might be appropriate together with a '--settle' flag, if/where available.

instead of manually opening things, i'd expect crypttab to be adjusted with `systemctl daemon-reload` re-run to regenerated systemd-cryptsetup@ units and "open" the encrytped device using systemd-cryptsetup@ instance unit.... However that might be "too" systemd specific for vaultcrypt upstream...

If one injects uuid onto a drive, it might not generate any kernel udev events for udevd to react to and create/update symlinks.

It would be nice to have an interleaved log of udev events from udevadm monitor, to see if there are any events emitted after "format" action is done. If there are none, then vaultlocker needs to be fixed to trigger things.