Bug 998122 - kmod-static-nodes.service fails to run in containers
Summary: kmod-static-nodes.service fails to run in containers
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-17 13:13 UTC by Jóhann B. Guðmundsson
Modified: 2013-08-21 01:34 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-21 01:34:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jóhann B. Guðmundsson 2013-08-17 13:13:53 UTC 
Description of problem:

When kmod-static-nodes.service is run within a container it fails with...
kmod-static-nodes.service: main process exited, code=exited, status=203/EXEC
[FAILED] Failed to start Create list of required static device nodes for the current kernel.
See 'systemctl status kmod-static-nodes.service' for details.
Unit kmod-static-nodes.service entered failed state.


Looks like we lack ConditionVirtualization= line which excludes the services from being run when in containers

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Zbigniew Jędrzejewski-Szmek 2013-08-19 14:59:38 UTC 
Upstream fix in 4bb3a126b7a6.
Comment 2 Zbigniew Jędrzejewski-Szmek 2013-08-21 01:34:03 UTC 
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4bb3a12 was actually about something different.

Fixed upstream in http://cgit.freedesktop.org/systemd/systemd/commit/?id=219061d. Also similar http://cgit.freedesktop.org/systemd/systemd/commit/?id=091526a was about GPT disks. I guess that those warnings are not very serious, so they can wait until the next release. So I'm closing this as FIXED/UPSTREAM, hopefully correctly.
Note You need to log in before you can comment on or make changes to this bug.