|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd-cryptsetup ignores timeout parameter of /etc/crypttab | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.3 | Reporter: | endym ion <endym> |
| Component: | Basesystem | Assignee: | systemd maintainers <systemd-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | axel.braun, bluedzins, fbui, fcrozat, RBrownCCB, thomas.blume, werner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | dmesg with systemd.log_level=debug (systemd lines only) | ||
|
Description
endym ion
2012-02-29 21:38:14 UTC
please boot with systemd.log_level=debug systemd.log_target=kmsg and attach dmesg output after rebooting ? Created attachment 479288 [details]
dmesg with systemd.log_level=debug (systemd lines only)
confirmed, systemd internal timeout is triggered on the dev-mapper node.. Hi,could you please look at this? I am not sure whether it is right to assign it to you.Feel free to reassign it whether necessary.Thank you. *** Bug 758081 has been marked as a duplicate of this bug. *** anything new on this issue? I need to discuss this with upstream 7 month later...and the problem still exists in 12.2 @Frederic: Anything new? Will you change the product 12.1 -> 12.2? I could change the product from 12.1 to 12.2 (or even Factory, although I didn't check if it was fixed), it wouldn't fix the bug :( I had no time to work on it, timeout is being correctly handled by cryptsetup, but the issue is in the systemd own timeout which is the issue.. (In reply to comment #9) > I could change the product from 12.1 to 12.2 (or even Factory, although I > didn't check if it was fixed), it wouldn't fix the bug :( Just asking because some bug owner like to keep it in the version the bug originally was detected. For regression tests. > I had no time to work on it, timeout is being correctly handled by cryptsetup, > but the issue is in the systemd own timeout which is the issue.. Any workaround so far? (In reply to comment #10) > > I had no time to work on it, timeout is being correctly handled by cryptsetup, > > but the issue is in the systemd own timeout which is the issue.. > > Any workaround so far? Unfortunately, no, current code is already setting "TimeoutSec=0" in the generated .service which is supposed to ensure timeout is correctly handled but other unit is timeouting (the one for the device, IIRC) (In reply to comment #10) > (In reply to comment #9) > > I could change the product from 12.1 to 12.2 (or even Factory, although I > > didn't check if it was fixed), it wouldn't fix the bug :( > > Just asking because some bug owner like to keep it in the version the bug > originally was detected. For regression tests. > > > I had no time to work on it, timeout is being correctly handled by cryptsetup, > > but the issue is in the systemd own timeout which is the issue.. > > Any workaround so far? Hi Axel, you will find a workaraound in the forum thread I mentioned at the end of the bug report. endym Upstream has just got a patch submission to fix this. I'll test it as soon as it is accepted. *** Bug 823823 has been marked as a duplicate of this bug. *** For the record, the workaround given on forum worked until OS 12.3 (i.e. in OS 12.3 the trick no longer works). *** Bug 823802 has been marked as a duplicate of this bug. *** Shouldn't we better move the bug to 12.3? yes.. I've tested a patch from upstream (it is supposed to be fixed in Factory already) but it doesn't seem to work as expected. I need to debug this further.. As this does not work for systemd 195 (openSUSE 12.3), I assume it affects 13.1 as well? no, as noted in my comment 18, it should be fixed in 13.1 (In reply to comment #20) > no, as noted in my comment 18, it should be fixed in 13.1 Is it possible to apply the patch to systemd 195? Work as expected on opensuse 13.1 so I'm tempted to close this one. (In reply to Franck Bui from comment #22) > Work as expected on opensuse 13.1 so I'm tempted to close this one. And it is fixed in newer versions, see bug 909912. Closing as fixed in current version. |