Bug 866128

Summary:	/usr/lib/systemd/system/mediatomb.service contains hardcoded network interface
Product:	[Fedora] Fedora	Reporter:	hostmaster
Component:	mediatomb	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17	CC:	gwync, humpf, jdy
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-12 00:20: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:

Description hostmaster 2012-10-14 08:05:09 UTC

Description of problem:


Version-Release number of selected component (if applicable):
mediatomb-0.12.1-16.fc17.x86_64

How reproducible:
You may have no eth0 interface, e.g. em1 (may default after fresh Fedora 17 installation)

Steps to Reproduce:
1. Fresh Fedora 17 installation, ethernet is named em1, not eth0
2. Install Mediatomb
3. Try to start with systemctl start mediatomb.service
  
Actual results:
/var/lob/mediatomb
ERROR: Could not find interface: eth0

Expected results:
Mediatomb shoul start w/o errors

Additional info:
/usr/lib/systemd/system/mediatomb.service contains hardcoded options, which prevent successful start up. RPM post install script should either ask user for desired interface or read network interface from /etc/mediatomb.conf MT_INTERFACE

Comment 1 Gwyn Ciesla 2012-10-15 13:53:29 UTC

On mine, it's p2p1.  Someone will always have to customize.  You can copy the unit file to /etc/systemd/system and modify that.  Postinstall scripts cannot be interactive.

Comment 2 Willy Villard 2012-10-24 19:15:01 UTC

After an update from mediatomb-0.12.1-16.fc17 to mediatomb-0.12.1-19.fc17, unit file changed. No change needed or unit file should be updated according values defined in mediatomb.conf

Comment 3 Fedora Update System 2012-10-30 14:57:16 UTC

mediatomb-0.12.1-20.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-20.fc18

Comment 4 Fedora Update System 2012-10-30 20:16:26 UTC

Package mediatomb-0.12.1-20.fc18:
* 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 mediatomb-0.12.1-20.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17263/mediatomb-0.12.1-20.fc18
then log in and leave karma (feedback).

Comment 5 Joel 2012-12-02 18:45:41 UTC

Why is $MT_USER being used for the group instead of $MT_GROUP?

Also, will this be pushed for fc17?

Thanks!

Comment 6 Joel 2012-12-02 18:49:31 UTC

Context for my comment above:

/usr/lib/systemd/system/mediatomb.service, ExecStart line

Comment 7 Gwyn Ciesla 2012-12-03 14:30:37 UTC

Because I apparently needed coffee. :)  I'll fix that and push to f17.

Comment 8 Fedora Update System 2012-12-03 14:51:39 UTC

mediatomb-0.12.1-21.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-21.fc18

Comment 9 Fedora Update System 2012-12-03 14:51:51 UTC

mediatomb-0.12.1-21.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-21.fc17

Comment 10 Fedora Update System 2012-12-12 00:20:53 UTC

mediatomb-0.12.1-21.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2012-12-12 04:34:28 UTC

mediatomb-0.12.1-21.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.