Bug 287291

Summary: kadmin doesn't start when LDAP backend is used
Product: [Fedora] Fedora Reporter: Fran Taylor <narf>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.6.1-6.fc7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-13 00:15:29 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 373011    
Attachments:
Description Flags
(very short!) patch to /etc/init.d/kadmin to allow it to start when LDAP is used none

Description Fran Taylor 2007-09-12 02:01:09 EDT
Description of problem:

/etc/init.d/kadmin doesn't start kadmin server when using LDAP backend

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


How reproducible:


Steps to Reproduce:
1. set up kerberos to use LDAP back end
2. attempt to start kadmin: /etc/init.d/kadmin start
3.
  
Actual results:

kadmin doesn't start

Expected results:

kadmin should start

Additional info:
Comment 1 Fran Taylor 2007-09-12 02:01:09 EDT
Created attachment 193271 [details]
(very short!) patch to /etc/init.d/kadmin to allow it to start when LDAP is used
Comment 2 Nalin Dahyabhai 2007-11-09 10:43:46 EST
Fixed in Raw Hide and F8, leaving open until I can get F7 and FC6 updates out.
Comment 3 Fedora Update System 2007-12-06 12:39:48 EST
krb5-1.6.1-6.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update krb5'
Comment 4 Fedora Update System 2008-02-13 00:15:18 EST
krb5-1.6.1-6.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.