Bug 1128376

Summary: fedmsg-notify-daemon does not start
Product: [Fedora] Fedora Reporter: Paulo Roma Cavalcanti <promac>
Component: fedmsg-notifyAssignee: Luke Macken <lmacken>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: lmacken, pfrields, rbean
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-19 15:11:31 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:

Description Paulo Roma Cavalcanti 2014-08-09 17:42:57 UTC
Description of problem:

After the release of:

python-fedmsg-meta-fedora-infrastructure-0.2.15-2.fc20.noarch
python-moksha-hub-1.4.0-1.fc20.noarch
fedmsg-0.9.0-1.fc20.noarch

/usr/bin/fedmsg-notify-daemon does not start.

Just call, and get:

/usr/bin/fedmsg-notify-config

org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/fedmsg-notify-daemon exited with status 1


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


How reproducible:

Always.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: