Bug 1310041

Summary: start job for missing device time out
Product: [Fedora] Fedora Reporter: Paul DeStefano <prd-fedora>
Component: systemdAssignee: systemd-maint
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 17:57:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
debug boot log (dmesg) as described in systemd debugging document none

Description Paul DeStefano 2016-02-19 10:15:20 UTC
Created attachment 1128500 [details]
debug boot log (dmesg) as described in systemd debugging document

Description of problem:
A start job stalls for a device that I cannot find and then times out.

Version-Release number of selected component (if applicable):
systemd-222-14.fc23.x86_64

How reproducible:
Every boot

Steps to Reproduce:
1. Unknown.  I don't know what this device used to be or what happened to it.  I also don't understand why there is a start job for it if it doesn't exist.

Actual results:
Start up is delayed 1m30s until job fails.

Expected results:
Job shouldn't exist/get created at boot.

Additional info:
I really tried to figure this out, myself, but I don't understand where this type of device-specific start job comes from or is configured.  Sorry, I just don't know systemd very well.h

Comment 1 Paul DeStefano 2016-05-10 17:57:51 UTC
This turned out to be a bad encrypted swap configuration.  See Bug 1304995.  After I changed /etc/crypttab, this bogus device start job disappeared.