Bug 1023293 - sssd is stopped after authconfig --enableipav2 --ipav2join
Summary: sssd is stopped after authconfig --enableipav2 --ipav2join
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: authconfig
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: David Spurek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-25 06:36 UTC by David Spurek
Modified: 2015-03-02 05:28 UTC (History)
6 users (show)

Fixed In Version: authconfig-6.1.12-17.el6
Doc Type: Bug Fix
Doc Text:
No doc text needed
Clone Of:
Environment:
Last Closed: 2014-10-14 07:44:51 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1558 0 normal SHIPPED_LIVE authconfig bug fix and enhancement update 2014-10-14 01:27:53 UTC

Description David Spurek 2013-10-25 06:36:32 UTC
Description of problem:
sssd is stopped after authconfig --enableipav2 --ipav2join
More info in steps to reproduce


Version-Release number of selected component (if applicable):
authconfig-6.1.12-13.el6

How reproducible:


Steps to Reproduce:
1.rm -f /etc/sysconfig/authconfig
2.authconfig --disablesssd --disablesssdauth --update --nostart
3.authconfig --enableipav2 --ipav2domain=<domain> --ipav2server=<domain server> --ipav2realm=<realm> --ipav2join=<user used to join> --update
4. service sssd status
5. getent passwd user@domain

Actual results:
sssd is stopped
getent doesn't return information about user

Expected results:
sssd should run
getent returns user information

Additional info:

Comment 2 Axel Thimm 2014-04-30 08:16:18 UTC
It also seems to happen with a simple --enablesssd.

Comment 3 Tomas Mraz 2014-04-30 08:19:24 UTC
Axel, are you talking about authconfig in RHEL-6?

Comment 7 errata-xmlrpc 2014-10-14 07:44:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1558.html


Note You need to log in before you can comment on or make changes to this bug.