diff options
| author | Birger Schacht <birger@rantanplan.org> | 2020-06-14 22:03:47 +0200 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2020-07-13 09:00:00 +0300 |
| commit | fd84747d5bd9cb052b151893c929b721f80de6dd (patch) | |
| tree | f60f24f17f033465848b66722ed2cdcaad13e57f | |
| parent | e5892c6f131b588b216b122f04f93593d38df2f8 (diff) | |
| download | vmdb2-fd84747d5bd9cb052b151893c929b721f80de6dd.tar.gz | |
Use batch mode of cryptsetup
Without batch mode, cryptsetup asks for confirmation before doing a
luks format of a device. When using vmdb, the user does not see the
prompt and cryptsetup just sits there and waits for confirmation.
Using --batch-mode or -q supresses this requirement for confirmation.
| -rw-r--r-- | vmdb/plugins/luks_plugin.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/vmdb/plugins/luks_plugin.py b/vmdb/plugins/luks_plugin.py index 9ea066c..531d570 100644 --- a/vmdb/plugins/luks_plugin.py +++ b/vmdb/plugins/luks_plugin.py @@ -75,7 +75,7 @@ class CryptsetupStepRunner(vmdb.StepRunnerInterface): state.tags.get_builder_mount_point(t)) assert 0 - vmdb.runcmd(['cryptsetup', 'luksFormat', dev, key_file]) + vmdb.runcmd(['cryptsetup', '-q', 'luksFormat', dev, key_file]) vmdb.runcmd( ['cryptsetup', 'open', '--type', 'luks', '--key-file', key_file, dev, crypt_name]) |