Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 785791

Summary: ipactl :: kpasswd service is no longer needed should not output stop|start|status information
Product: Red Hat Enterprise Linux 6 Reporter: Jenny Severance <jgalipea>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED WONTFIX QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: mkosek, ssorce
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-07 14:18:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jenny Severance 2012-01-30 16:08:45 UTC
Description of problem:

# ipactl status
Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING

# ipactl stop
Stopping CA Service
Stopping pki-ca:                                           [  OK  ]
Stopping HTTP Service
Stopping httpd:                                            [  OK  ]
Stopping DNS Service
Stopping named: .                                          [  OK  ]
Stopping KPASSWD Service
Stopping Kerberos 5 Admin Server:                          [  OK  ]
Stopping KDC Service
Stopping Kerberos 5 KDC:                                   [  OK  ]
Stopping Directory Service
Shutting down dirsrv: 
    PKI-IPA...                                             [  OK  ]
    TESTRELM-COM...                                        [  OK  ]


# ipactl start
Starting Directory Service
Starting dirsrv: 
    PKI-IPA...                                             [  OK  ]
    TESTRELM-COM...                                        [  OK  ]
Starting KDC Service
Starting Kerberos 5 KDC:                                   [  OK  ]
Starting KPASSWD Service
Starting Kerberos 5 Admin Server:                          [  OK  ]
Starting DNS Service
Starting named:                                            [  OK  ]
Starting HTTP Service
Starting httpd: [Mon Jan 30 11:07:04 2012] [warn] worker ajp://localhost:9447/ already used by another worker
[Mon Jan 30 11:07:04 2012] [warn] worker ajp://localhost:9447/ already used by another worker
                                                           [  OK  ]
Starting CA Service
Starting pki-ca:                                           [  OK  ]



Version-Release number of selected component (if applicable):
ipa-server-2.2.0-101.20120127T0607zgit6863b8f.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

note warning displayed on start is logged in another bug

Comment 1 Martin Kosek 2012-01-31 16:10:27 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2333

Comment 2 Rob Crittenden 2012-02-03 16:46:01 UTC
ipa_kpasswd went away but a new service is being run in its stead, the standard kadmind service.

Simo purposely set the name to kpasswd.

Comment 3 Jenny Severance 2012-02-03 16:54:45 UTC
# ps -ef | grep krb5kdc
root      4760     1  0 11:12 ?        00:00:00 /usr/sbin/krb5kdc -r TESTRELM.COM -P /var/run/krb5kdc.pid
root      5613  8022  0 11:53 pts/0    00:00:00 grep krb5kdc


# ps -ef | grep kadmind
root      4776     1  0 11:12 ?        00:00:00 /usr/sbin/kadmind -P /var/run/kadmind.pid
root      5619  8022  0 11:53 pts/0    00:00:00 grep kadmind

# ps -ef | grep kpasswd
root      5623  8022  0 11:53 pts/0    00:00:00 grep kpasswd


This is confusing ....

Comment 4 Rob Crittenden 2012-02-03 21:17:42 UTC
Simo, QE finds your choice of KPASSWD to mean kadmind confusing. I have to say I agree. What was your rationale?

Comment 5 Simo Sorce 2012-02-03 23:28:16 UTC
A) it was the existing service name, by not changing it we do not have a problem upgrading.
B) we really use kadmin exclusively for the kpasswd functionality, all other functions are basically disabled in the ipa-kdb backend.

Comment 6 Martin Kosek 2012-02-24 09:31:41 UTC
If this is resolved, I believe we should just close this BZ as wontfix. It is already closed as wontfix upstream.

Comment 7 Jenny Severance 2012-02-24 15:05:35 UTC
It is still confusing as someone may look for this service because it is listed as a running or stopped service..   If I did a "ipactl status" and it said the kpasswd was not running ... I would try "service kpasswd start" and ... it would fail.  This is not resolved.

Comment 8 Rob Crittenden 2012-02-24 18:25:18 UTC
I don't think the names we display will be confused with an actual service name considering we don't use actual service names in the output.

Comment 9 Rob Crittenden 2012-03-07 03:09:07 UTC
The current output looks like this. This explains what I mean about service names not being in the output:

Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
MEMCACHE Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING

None of these are actual unix service names.

Comment 10 Jenny Severance 2012-03-07 12:54:06 UTC
okay, will change my tests and lets mark this resolved