Bug 951866

Summary:	SystemD-201.2 fails to process "EnvironmentFile=/etc/sysconfig/xxxxxx"
Product:	[Fedora] Fedora	Reporter:	Steve Foster <steve_a_foster>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	18	CC:	johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-201-2.fc18.6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-16 03:01:18 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:

Description Steve Foster 2013-04-13 23:32:17 UTC

Description of problem:
Systemd appears to not process "EnvironmentFile" 

Version-Release number of selected component (if applicable):
201-2.fc18.2.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Update systemd from updates-testing
2. Re-boot and lm_sensors.service fails
3.
  
Actual results:
lm_sensors.service  never loads module from /etc/sysconfig/lm_sensors

Expected results:
Module in Config file should work.

Additional info:
Downgrade back to previous systemd and back to normal.

Sigh....

Comment 1 Steve Foster 2013-04-13 23:37:51 UTC

Another report on the same exact problem in another Distro but same packages

https://bbs.archlinux.org/viewtopic.php?pid=1258733

Comment 2 Michal Schmidt 2013-04-15 13:47:36 UTC

Fixed upstream by Zbigniew:

http://cgit.freedesktop.org/systemd/systemd/commit/?id=d3b6d0c21ea5a0d15ec6dbd8b8d179138b7463bc

Comment 3 Fedora Update System 2013-04-15 14:20:16 UTC

systemd-201-2.fc18.3 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.3

Comment 4 Steve Foster 2013-04-15 21:25:42 UTC

Confirming the systemd update indeed fixes this issue I reported.

Comment 5 Fedora Update System 2013-04-16 00:04:27 UTC

Package systemd-201-2.fc18.4:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.4
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-04-18 02:42:01 UTC

Package systemd-201-2.fc18.5:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-05-07 13:44:06 UTC

systemd-201-2.fc18.6 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6

Comment 8 Fedora Update System 2013-05-09 10:05:21 UTC

Package systemd-201-2.fc18.6:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-05-16 03:01:18 UTC

systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.