https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c0
Summary: systemd asks cryptsetup password a bit too often Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat@suse.com ReportedBy: coolo@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: ---
This happens with other services too, so I don't think it's an openvpn problem, but not knowing how it works internally, I blame systemd:
goneril:/home/coolo # systemctl restart openvpn@SUSE.service Please enter passphrase for disk primary (cr_ata-HGST_HTS725050A7E630_TF755AWHG5NB8M-part5)! Enter Auth Username: ***** Please enter passphrase for disk primary (cr_ata-HGST_HTS725050A7E630_TF755AWHG5NB8M-part5)! Enter Auth Password: ************* Please enter passphrase for disk primary (cr_ata-HGST_HTS725050A7E630_TF755AWHG5NB8M-part5)!
At the beginning I always entered the passphrase, but I soon learned that it does not matter - the volume is mounted after all. part5 is my LVM - without it nothing here would do.
I'm still running systemd 207 as my factory is stalled at the time of 13.1 Beta, but this problem is older and I never reported it.
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c1
--- Comment #1 from Frederic Crozat fcrozat@suse.com 2013-11-04 10:48:52 UTC --- this is because openvpn is using the same 'ask-password' systemd infrastructure as cryptsetup and it starts by asking for password which weren't answered..
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c
Frederic Crozat fcrozat@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c2
systemd maintainers systemd-maintainers@suse.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com
--- Comment #2 from systemd maintainers systemd-maintainers@suse.de 2013-11-26 08:36:22 UTC --- (In reply to comment #1)
this is because openvpn is using the same 'ask-password' systemd infrastructure as cryptsetup and it starts by asking for password which weren't answered..
Is there any option like --accept-cached and --multiple which would avoid this?
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c3
Frederic Crozat fcrozat@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |fcrozat@suse.com InfoProvider|fcrozat@suse.com |
--- Comment #3 from Frederic Crozat fcrozat@suse.com 2013-12-06 12:05:52 UTC --- (In reply to comment #2)
(In reply to comment #1)
this is because openvpn is using the same 'ask-password' systemd infrastructure as cryptsetup and it starts by asking for password which weren't answered..
Is there any option like --accept-cached and --multiple which would avoid this?
Ohh, indeed, there is both of them (It seems to be already used by plymouth)..
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c
Dr. Werner Fink werner@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Other |openSUSE 13.1
https://bugzilla.novell.com/show_bug.cgi?id=848814
https://bugzilla.novell.com/show_bug.cgi?id=848814#c4
--- Comment #4 from Stephan Kulow coolo@suse.com 2014-06-25 14:14:15 CEST --- FYI: I don't have this problem in factory
http://bugzilla.novell.com/show_bug.cgi?id=848814
Stephan Kulow coolo@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #5 from Stephan Kulow coolo@suse.com --- seems fixed