Bug 963722

Summary: oddjob can not be started through d-bus
Product: [Fedora] Fedora Reporter: Patrik Kis <pkis>
Component: oddjobAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: nalin, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: oddjob-0.31.4-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 967025 (view as bug list) Environment:
Last Closed: 2013-05-29 03:04:57 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:
Bug Depends On:    
Bug Blocks: 959458, 964971, 967025    

Description Patrik Kis 2013-05-16 13:18:12 UTC
Description of problem:
I believe oddjob supposed to start based on d-bus request but currently it can be started only as a normal service and on top of that it cannot be enabled (it does not survive reboot).

Version-Release number of selected component (if applicable):
oddjob-0.31.3-3.fc19

How reproducible:
always

Steps to Reproduce:

# useradd -M qwe
# ls /home/qwe
ls: cannot access /home/qwe: No such file or directory
#
# su - qwe
org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.oddjob_mkhomedir was not provided by any .service files
Last login: Thu May 16 15:15:17 CEST 2013 on pts/1
su: warning: cannot change directory to /home/qwe: No such file or directory
-bash-4.2$ pwd
/root
-bash-4.2$ exit
logout
#
# systemctl start oddjobd.service
# su - qwe
Creating home directory for qwe.
Last login: Thu May 16 15:15:46 CEST 2013 on pts/0
$ pwd
/home/qwe
$ exit
logout
#

Comment 1 Nalin Dahyabhai 2013-05-17 22:05:09 UTC
(In reply to comment #0)
> Description of problem:
> I believe oddjob supposed to start based on d-bus request but currently it
> can be started only as a normal service and on top of that it cannot be
> enabled (it does not survive reboot).

FWIW, it originally wasn't designed to be started by the bus, as it predates the bus being able to start things.  The daemon can register multiple service names when it's started, which may complicate things if we're looking at bus activation.

Fixing the can't-start-as-a-regular-service part is easier.

Comment 2 Fedora Update System 2013-05-17 22:08:06 UTC
oddjob-0.31.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/oddjob-0.31.4-1.fc19

Comment 3 Fedora Update System 2013-05-18 17:57:09 UTC
Package oddjob-0.31.4-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing oddjob-0.31.4-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8506/oddjob-0.31.4-1.fc19
then log in and leave karma (feedback).

Comment 4 Patrik Kis 2013-05-20 08:42:07 UTC
The version oddjob-0.31.4-1.fc19 service can be enabled.

# systemctl disable oddjobd.service
# systemctl list-unit-files |grep oddjob
oddjobd.service                             disabled
# systemctl enable oddjobd.service
ln -s '/usr/lib/systemd/system/oddjobd.service' '/etc/systemd/system/multi-user.target.wants/oddjobd.service'
# systemctl list-unit-files |grep oddjob
oddjobd.service                             enabled 
# systemctl disable oddjobd.service
rm '/etc/systemd/system/multi-user.target.wants/oddjobd.service'
# systemctl list-unit-files |grep oddjob
oddjobd.service                             disabled
# /usr/sbin/authconfig --update --enablesssd --enablesssdauth --enablemkhomedir --nostart
# systemctl list-unit-files |grep oddjob
oddjobd.service                             enabled

Comment 5 Fedora Update System 2013-05-29 03:04:57 UTC
oddjob-0.31.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.